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
I renamed a migration file with a .txt extension to get the migration script to skip over it, but it was still processed as a JavaScript migration.
An easy work-around for me is to prefix the file name with an underscore _ instead so that it doesn't pass the timestamp length test. However, I don't recall seeing the error thrown about being an invalid file. I would have expected this to only parse javascript files with case-insensitive jscjs or mjs extensions.
The other day I tried associating SQL files in the same folder to get syntax highlighting and didn't realize what the issue was.
ie same name 1716831766170_create_function_uuid4.up.sql to keep it close to the migration script, and do a file.readSync on the sql file.
I renamed a migration file with a
.txt
extension to get the migration script to skip over it, but it was still processed as a JavaScript migration.An easy work-around for me is to prefix the file name with an underscore
_
instead so that it doesn't pass the timestamp length test. However, I don't recall seeing the error thrown about being an invalid file. I would have expected this to only parse javascript files with case-insensitivejs
cjs
ormjs
extensions.The other day I tried associating SQL files in the same folder to get syntax highlighting and didn't realize what the issue was.
ie same name
1716831766170_create_function_uuid4.up.sql
to keep it close to the migration script, and do a file.readSync on the sql file.mysql-migrations/core_functions.js
Lines 44 to 55 in 65c5208
The text was updated successfully, but these errors were encountered: