We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think that the migrations_script_directory config and the related executeScript(Database $db, $file) method add little value for the extra overhead.
migrations_script_directory
executeScript(Database $db, $file)
https://github.com/doesntmattr/mongodb-migrations/blob/master/src/AntiMattr/MongoDB/Migrations/Version.php#L261
It would be easy enough for anyone to load the javascript file and run it directly against $db in their own migration if they wanted it.
$db
I would like to make this feature deprecated to be removed in 3.0.
3.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I think that the
migrations_script_directory
config and the relatedexecuteScript(Database $db, $file)
method add little value for the extra overhead.https://github.com/doesntmattr/mongodb-migrations/blob/master/src/AntiMattr/MongoDB/Migrations/Version.php#L261
It would be easy enough for anyone to load the javascript file and run it directly against
$db
in their own migration if they wanted it.I would like to make this feature deprecated to be removed in
3.0
.The text was updated successfully, but these errors were encountered: