How to make migration to newer versions of templates more straightforward? #14244
MartinZikmund
started this conversation in
General
Replies: 1 comment 2 replies
-
Templates are not changing that often, once a year in a significant way, but in general, it's not required to upgrade to latest template and the previous structure still works. The only required steps are the ones that are breaking, which are detailed in the migration doc. Otherwise, if someone wants to update to the latest template structure, create and replace is likely the easiest solution for everyone. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently upgrading an existing solution to new versions of the template can be tricky. Users have three options:
All of these are quite error-prone. Is there a better approach available? Could we have some semi-automated migration tool? The "manual" way would be that each PR in Uno.Templates would also require a change to the release migration docs in Uno repo
Beta Was this translation helpful? Give feedback.
All reactions