Fix phantom migration rollback failures caused by cross-branch acronyms #108
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
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.
Closes #95
Description
Phantom migration rollbacks were failing due to differences in acronym-inflection settings between branches. Rails relies on the current environment's inflector to derive class names from migration file names, leading to a mismatch when acronyms are defined inconsistently across branches.
To resolve this, the migration class name is now directly extracted from the migration file instead of relying on Rails' inflection logic. This ensures accurate class loading and successful rollbacks regardless of acronym definitions in other branches.