fix(core): update move generator to move multiple projects in eslint parserOptions override #10775
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.
move generator now copies over all projects in the parserOptions of the .eslintrc.json rather than
just overriding with the base tsconfigs
ISSUES CLOSED: #10774
Current Behavior
To move an existing library, we run the following
In our case, the move does not keep the storybook config file in
.eslintrc.json
after the move. This is underoverrides > parserOptions > projects
. It overrides it with just the base tsconfigs.Before the move, the
eslintrc.json
looks like like this:When you run the move command, the new
eslintrc.json
will look like this:Expected Behavior
The generator now copies all projects from the existing array, and updates the project root to the new path, no longer dropping any config files. This results in the following output in
.eslintrc.json
Related Issue(s)
Fixes #10774