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

support for module migrations #5

Open
yogthos opened this issue Jan 9, 2022 · 0 comments
Open

support for module migrations #5

yogthos opened this issue Jan 9, 2022 · 0 comments
Labels
enhancement New feature or request generator Issue relating to kit-generator or code generation good first issue Good for newcomers help wanted Extra attention is needed

Comments

@yogthos
Copy link
Collaborator

yogthos commented Jan 9, 2022

Currently, modules write to install-log.edn whether the module was installed successfully or not. Instead, it would be better to create a map containing install information such as the version of the module that was installed as well as other metadata such as the files that were modified.

This would allow modules to provide a :migrations key under :actions. Migrations would work similarly to :injections, but would instead look for code generated by the previous version of the module and replace it with the updated code from the latest version.

@yogthos yogthos added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Jan 9, 2022
@nikolap nikolap added the generator Issue relating to kit-generator or code generation label Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request generator Issue relating to kit-generator or code generation good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants