Added migrationsList helper to easily build a valid list of migrations #199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
This PR brings a solution to a problem that has already been reported, notably in this issue: #184 . This older PR also attempts to bring a solution for that: #188 .
This issue is that the documentation specifies that it is possible to avoid using an automatic file loader for migrations and to specify a list of migrations instead. (Notable use case where we need to do this is when we use Webpack, where a file loader usually won't work as expected.) Unfortunately this is not particularly easy to do. The
Migration
class is not exposed in theindex.js
file and, even by importing it anyway, it's still not easy to use because it is very oriented toward that migration-file-loading behavior.This PR simply adds an utility function named
migrationsList()
that allow to specify a list of migrations this way:I added a test and documented the feature.