Server-side registering of Package Manif...
# news
c
📣 New post: Server-side registering of Package Manifest in Umbraco 14 https://dev.to/skttl/server-side-registering-of-package-manifest-in-umbraco-14-49go
w
oooooohhhhh off to read....
Neat approach @skttl 💪
So that Extensions object is mandatory. Did you try hacking the planet and trying to register something server side for the client ?
a
I'm also doing this for Skybrud Redirects and some unreleased packages. https://github.com/skybrud/Skybrud.Umbraco.Redirects/blob/v14/main/src/Skybrud.Umbraco.Redirects/Manifests/RedirectsPackageManifestReader.cs For one, I can set the package version from C#. In Umbraco 12 and 13, one could specify a package ID, and Umbraco would grab the version number from the DLL if the package ID and assembly name aligned. But from what I can tell, this isn't possible in Umbraco 14. For now for Skybrud Redirects, I'm adding the entry point and an import map, but I'd might add other extension from C# going forward. The
Extensions
property is a collection of
object
, so there isn't much intellisense C#-wise. I have thought about introducing my own classes to mimic the data structure for various extension types. But I probably have to work on a few more packages before I know whether this actually makes sense.
w
Yeh could do with an inverse of scanning the interfaces in TS for Extension Manifest types to generate C# classes
Neat stuff gang - I haven't had a need as of yet to register with C#
3 Views