You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When initializing migrate with a file source, we noticed that migrate silently ignores bad file paths (i.e. 003_some_migration.up copy.json). We don't expect migrate to allow these bad filenames to run, but we were stumped for some time on why a particular migration didn't run (we hadn't noticed the bad filename).
Describe the solution you'd like
We would like to initialize migrate in a more "strict" way, i.e. fail when there are bad filepaths in the source location, or provide us with a function to validate our source location before initializing migrate.
Describe alternatives you've considered
What we currently do is use the regex from source/parse.go in a validate function and run it against our migration directory.
Additional context
Happy to elaborate more if needed.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When initializing migrate with a
file
source, we noticed that migrate silently ignores bad file paths (i.e.003_some_migration.up copy.json
). We don't expect migrate to allow these bad filenames to run, but we were stumped for some time on why a particular migration didn't run (we hadn't noticed the bad filename).Describe the solution you'd like
We would like to initialize migrate in a more "strict" way, i.e. fail when there are bad filepaths in the source location, or provide us with a function to validate our source location before initializing migrate.
Describe alternatives you've considered
What we currently do is use the regex from
source/parse.go
in a validate function and run it against our migration directory.Additional context
Happy to elaborate more if needed.
The text was updated successfully, but these errors were encountered: