Observing node name changes not working in v17 backoffice

[sussexrick]

Which Umbraco version are you using?

17.0.0-rc1

Bug summary

In a backoffice block preview using UMB_CONTENT_WORKSPACE_CONTEXT and observing context.name() does not work.

Specifics

I am trying to create a backoffice preview for a block which displays the current content node name.

Using UMB_CONTENT_WORKSPACE_CONTEXT I can use context.getName() to get the name at the time the page is loaded. However, observing context.name() to watch for changes doesn't work. The parameter passed to the callback is always empty, and the backoffice preview only updates after you save, move away from that content item, and then move back to it.

See https://forum.umbraco.com/t/how-do-i-get-the-node-name-from-a-block-editor-view/6522/2 for more context. I could not find any documentation for how to do this, so it could be that the approach suggested in the forum response is wrong.

Steps to reproduce

This is a repro using 17.0.0-rc1 and the default starter kit. I have not created or modified any content, only added the Client folder.

Expected result / actual result

I believe the intended behaviour of the new backoffice is to make updates to things like node name available earlier. I'm not sure whether this is as they're typed, when you tab away from the field, or when you save, but I do not expect to need to move away from the content and back again to see an update.

[github-actions]

Hi there @sussexrick!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[nielslyngsoe]

Hi @sussexrick

I'm not aware that this has changed, it may have, but then I will see your previous working situation as slightly a mistake.

This would only work if your Document is not varying by culture.
If that is your case, then this will fix your issue:
#20768

But I would advice you to use the Property Dataset, this holds the data specific to the Variant, also the variant name.
You can read my arguments and a suggested fix here:
https://forum.umbraco.com/t/how-do-i-get-the-node-name-from-a-block-editor-view/6522/4

Please confirm wether this previously was only working on invariant document, or if it also worked on variant documents. — For that reason I put the tag needs-more-info.

Thanks in advance

[sussexrick]

@nielslyngsoe Thank you, your solution works perfectly. I believe we were only using it with variants before as the AngularJS version was editorState.current.variants.filter(x => x.active)[0].name.

[nielslyngsoe]

@sussexrick great to know.

And thanks for the insight into your previous v.13 solution — surely an example of code we are happy to provide other ways for, cause its very coupled to the specific data models.