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
Cop doesn't detect violations for rails 6+ multi database project where there are different 'migrations_paths' for each database. It only works for violations for the main database with migrations residing in the 'migrate' folder.
Expected behavior
Cop should detect violations for all database migrations
Actual behavior
Only detect violations for database migrations inside 'migrate' folder and discards all other migrations.
Steps to reproduce the problem
Database.yml from the guides example for rails multi databases. Any migration inside 'db/animals_migrate' doesn't get reported for violations.
Cop doesn't detect violations for rails 6+ multi database project where there are different 'migrations_paths' for each database. It only works for violations for the main database with migrations residing in the 'migrate' folder.
Expected behavior
Cop should detect violations for all database migrations
Actual behavior
Only detect violations for database migrations inside 'migrate' folder and discards all other migrations.
Steps to reproduce the problem
Database.yml from the guides example for rails multi databases. Any migration inside 'db/animals_migrate' doesn't get reported for violations.
RuboCop version
1.13.0 (using Parser 3.0.1.0, rubocop-ast 1.4.1, running on ruby 3.0.1 x86_64-darwin20)
The text was updated successfully, but these errors were encountered: