Did something change with the way trees
# package-development
p
Did something change with the way trees are handled from v14 to v15? I had a working tree on v14, but upgrading it to v15 and nothing is showing. Now trying to figure out where it is coming from
Nvm, I used the wrong typing. Should have been ManifestMenuItemTreeKind instead of ManifestMenuItem
n
So was it just a TypeScript compilation error? or was the difference to add
kind: 'tree'
in your manifest?
p
I had it as
: any
first and thought that the type that I needed was ManifestMenuItem which also removed some properties. I thought that was just part of the v14 -> v15 migration, but it was because I was using the wrong typing
n
Hi Patrick, I would say when defining Manifests, its not ideal to be so specific about the type, but instead use the Type for all Extension Types of your project. You can read more about it here: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest#type-intellisense It is new for v.15 that we have this type — It enables you to declare your own types in your project that they will then take part in this Type. As well other packages can expose their types and by including those in your tsconfig they will also become valid choices in your Manifests. I hope that helps going forward 🙂