fix(migrations): passed in paths will be respected in nx workspaces#52796
fix(migrations): passed in paths will be respected in nx workspaces#52796jessicajaniuk wants to merge 1 commit intoangular:mainfrom
Conversation
This fixes a bug where if you have multiple tsconfig files, the migration would not find anything to migrate at the passed in path. fixes: angular#52787
|
@dgp1130 could you please help with the review for this PR? |
dgp1130
left a comment
There was a problem hiding this comment.
LGTM.
This does seem to be a somewhat recurring problem with tsconfig paths in Nx workspaces. I wonder if would be worth stepping back separately from this PR and looking at the problem a little more wholistically. Are there improvements we could make to testing or our schematics infrastructure which would catch this problem or make it "just work" by default without having to think about it?
|
This PR was merged into the repository by commit da97bbc. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…ngular#52796) This fixes a bug where if you have multiple tsconfig files, the migration would not find anything to migrate at the passed in path. fixes: angular#52787 PR Close angular#52796
…ngular#52796) This fixes a bug where if you have multiple tsconfig files, the migration would not find anything to migrate at the passed in path. fixes: angular#52787 PR Close angular#52796
…ngular#52796) This fixes a bug where if you have multiple tsconfig files, the migration would not find anything to migrate at the passed in path. fixes: angular#52787 PR Close angular#52796
This fixes a bug where if you have multiple tsconfig files, the migration would not find anything to migrate at the passed in path. fixes: #52787
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?