Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future: (IDEA) Versioning Standard Elements and Gum Forms #415

Open
kaltinril opened this issue Dec 27, 2024 · 0 comments
Open

Future: (IDEA) Versioning Standard Elements and Gum Forms #415

kaltinril opened this issue Dec 27, 2024 · 0 comments

Comments

@kaltinril
Copy link
Collaborator

Look into versioning the objects.

The reason I'm thinking about this, is, if someone has an old project and something isn't working, or, if someone has an old project and they want to get new features, we don't want to break their old project.

Version using semantic versioning or some scheme where the primary version number is upgraded only when breaking changes are introduced. So Version 3.0, 3.2, 3.4.2, etc are all backwards compatible to any version before within the 3.0 release.

Then, someone could "pick" the version of the items they want to target. In the future this would allow us to target upgrades for standard elements and forms components without breaking things.

It would also lead nicely into the future ability to "upgrade" forms component install without creating a fresh project and manually moving gumx files around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant