V15.1 - Cannot create/register a 'dynamicRootQueryStep' or 'dynamicRootOrigin' extension

[warrenbuckley]

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

15.1.0

Bug summary

I am unable to create/register a manifest of type dynamicRootQueryStep or dynamicRootOrigin

Specifics

No response

Steps to reproduce

• Create an Umbraco extension (outside of the mono repo of Umbraco)
• Try to register a manifest with TypeScript of the type 'dynamicRootQueryStep'
• See build error or no completions for the manifest type property

export const manifests: Array<UmbExtensionManifest> = [
    {
        name: "Taxonomy Manager - Dyanmic Root Query Step - Enabled Taxonomies",
        alias: "TaxonomyManager.Client.DynamicRootQueryStep.EnabledTaxonomies",
        type: "dynamicRootQueryStep",
        meta: {
            queryStepAlias: 'MyCustom',
            label: 'Only if enabled property is true',
            description: 'Query nodes that have the property "enabled" and is set to true',
            icon: 'icon-circle-dotted-active',
        }
    }
]

Expected result / actual result

That this builds and registers the manifest correctly.
My assumption is that the type is not exported into a package that consume the NPM package, but I am not 100% sure

[github-actions]

Hi there @warrenbuckley!

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

[warrenbuckley]

My current workaround for now to carry on with work is to register this via umbraco-package.json