Only use files with the correct extension for migrations #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tgriesser
added a commit
that referenced
this pull request
Dec 12, 2013
…st-all Only use files with the correct extension for migrations
|
Ah, good call, thanks @lmorchard! |
JakobJoonas
pushed a commit
to JakobJoonas/knex
that referenced
this pull request
Sep 23, 2022
* Document changes in migration config * Add documentation for initial param setup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When editing migrations in VIM, I noticed that Knex was picking up the
.swpfiles and throwing an error. This commit filters by extension for just the expected files.I didn't code up a full-blown test, but the addition of a random crap file in the migration fixtures will trigger the error that this commit fixes.