But how can I use different Configs for my macros? Currently they all run the same bundled Custom UI frontend. And currently in the UI Kit 1 world I define the config in the manifest.yml like so:
I’m not sure what your Config code looks like (if there’s overlap), but it’s definitely possible to use conditionals. You can use the view.getContext method and implement different logic based on the resulting moduleKey (which matches what you find in your manifest).
There might be a better way in general, but that should work.
Nice summary. My blockers are mostly missing Boolean form controls. (See post below)
But how in the world does Atlassian want us to migrate and then the stuff does not work In the CHANGELOG-1932 is stated that within 6 months UI Kit 1 will no longer work!
Yeah I can’t migrate until that re-render one is fixed.
It’s likely they’ll extend the deprecation date. But they do need to be more cautious with deprecating Forge packages. I wish it was made clear years ago that UI Kit was a server-side runtime that would be shutdown in the future, and not just a UI component library like Atlaskit.
Your best bet is to contact developer support and insist they create tickets for each of the issues you’ve found.
Good idea. I have opened ECOHELP-50788 and asked them to open ECO-X tickets.
Let’s see if they actually do this and/or if they stay forever in some backlog