liftedinit / liftedinit/many-rs
[tracking] Migration framework improvements
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
List of QoL improvements.
- [ ] List the migrations missing from the configuration file [1]
- Note: Moot if we implement the next point
- [ ] Add sane defaults for migrations not specified in the configuration file
- [ ] Remove complete explicit migration listing in the configuration file
- [ ] Add a flag to output the migration list to JSON (analog to `--list-migrations`)
- [ ] Activate new code behavior by default on new storage
- [ ] Think of a sane way to test legacy code, migrations, and new code
- [ ] Port migrations to json5. It depends on [2]
- [ ] Add a `create_migration!` macro
Future considerations
- [ ] Implement incompatible migrations support and validation
- [ ] Add support for running migrations in a given order (on the same block)
[1]: https://github.com/liftedinit/many-framework/pull/278#discussion_r1019469071
[2]: https://github.com/liftedinit/many-rs/issues/217
Contributor guide
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
This is a tracking list with no files or tests named. Start by selecting one unchecked migration-framework item, then read the PR #278 discussion and issue #217 dependency. Define acceptance criteria for the selected configuration, JSON output, storage behavior, or macro change and add focused tests before considering it done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100