Refactor AnnotateRoutes by adding AnnotateRoutes::HeaderGenerator #790
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.
I noticed that
AnnotateRoutes
can be more maintainable by refactoring.I am planning to refactor
AnnotateRoutes
in this order.AnnotateRoutes
intoAnnotateRoutes::HeaderGenerator
.AnnotateRoutes::HeaderGenerator
and refactor methods.AnnotateRoutes::AnnotationProcessor
andAnnotateRoutes::RemovalProcessor
The final goal of this refactoring is as follows.
So in the first I added
AnnotateRoutes::HeaderGenerator
in order to separate logic ofAnnotateRoutes
in this PR.When refactor of
AnnotateRoutes
is finished, I would like to refactorAnnotateModels
in a like way.