refactor(kube-api-rewriter): renaming before refactoring rewrites #153
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.
Description
NOTE: No significant changes in rewriters are made, except simple refactoring in some places:
@Root
path for all transformers.Main changes:
Why do we need it, and what problem does it solve?
It is the first step in rewriters code optimization. Open a separate PR to reduce renaming noise in the next PRs.
What is the expected result?
Everything works as before, even bugs.
Checklist