refactor(@angular-devkit/schematics): Delete 'rename' rule #24000
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.
rename
rule.PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The
rename
rule exists in the source and is packaged, but is not exposed via the entrypoints.Issue Number: N/A
What is the new behavior?
The
rename
rule is deleted from the source, as it was decided it was no longer wanted.Does this PR introduce a breaking change?
Other information
Note that the rule can be referenced directly, such as through a statement like this:
import { rename } from '@angular-devkit/schematics/src/rules/rename.js';
. However, since that isn't part of the publicly exposed API, deleting it shouldn't be considered a breaking change.