v15.1-rc - ' UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE' export has moved - breaking change?

[KevinJump]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

v15.1-rc

Bug summary

It looks like the export of the 'UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE' has been moved
and hence if you have extension code that imports the type it fails on v15.1 with the following :

'@umbraco-cms/backoffice/document-type' does not provide an export named 'UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE'

Specifics

It looks like the export of the 'UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE' has been moved
and hence if you have extension code that imports the type it fails on v15.1 with the folllowing :

'@umbraco-cms/backoffice/document-type' does not provide an export named 'UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE'

Steps to reproduce

On v15 extension code can import the UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE using:

import { UMB_DOCUMENT_TYPE_FOLDER_ENTITY_TYPE,} from '@umbraco-cms/backoffice/document-type';

this doesn't work from v15.1-rc as the import has moved.

N.B: I can't test what the new value as is there is no published v15.1-rc version of the backend client package on npm?

existing client code built against v15 breaks because of this.

Expected result / actual result

client side extensions build against the v15 umbraco back office package should still work when running against v15.1 versions of Umbraco

---

This item has been added to our backlog AB#46666

[github-actions]

Hi there @KevinJump!

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 🤖 🙂

[bergmania]

Thanks for letting us know.. We'll look into it

[nielslyngsoe]

Hi @KevinJump Thanks for informing us about this one. To prevent this ever happening again I took the time to make a test that ensures consts starting by UMB_ is exposed. So hopefully the last time you would have to repport an issue like this.

Thanks in advance.