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

Diagnostic Support for Adding Migrations #341

Open
MavenRain opened this issue Mar 23, 2023 · 0 comments
Open

Diagnostic Support for Adding Migrations #341

MavenRain opened this issue Mar 23, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@MavenRain
Copy link
Contributor

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.

@MavenRain MavenRain added the enhancement New feature or request label Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant