support for module migrations
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 558
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the module installation handling around install-log.edn. Clarify the metadata map and how module :actions should expose :migrations alongside :injections; done means recording installation metadata and replacing code generated by a previous module version with updated code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100