liftedinit / liftedinit/many-rs
Diagnostic Support for Adding Migrations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if you add a new migration to `ledger_migrations.json`, and the name entry of that migration does not exactly match the name entry in the migration code, e2e migration and staging tests fail with a vague "Unsupported migration". Ideally, the name of the unsupported migration should be added to the error message, along with all of the migrations that are supported, so that the developer previously unfamiliar with the migration framework can spot the difference, particularly if it is a simple typo.
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
Start by reviewing the migration names in ledger_migrations.json and run the e2e migration and staging tests to reproduce the vague "Unsupported migration" error. Trace the migration framework entry point that produces this message. Done means the error identifies the unsupported name and lists all supported migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100