-
Notifications
You must be signed in to change notification settings - Fork 9
Rename and restructure classes and packages #125
Copy link
Copy link
Open
Labels
brainstormingIdea for a potential new feature or adaption that still needs further discussionIdea for a potential new feature or adaption that still needs further discussioncode qualityTopics around code quality, e.g. refactoring, better naming of methods/classesTopics around code quality, e.g. refactoring, better naming of methods/classescomments welcomeIndicates that the creator of this issue/PR is open for early review commentsIndicates that the creator of this issue/PR is open for early review commentspriority:lowShould be quite a far way down on the agendaShould be quite a far way down on the agenda
Milestone
Description
Metadata
Metadata
Assignees
Labels
brainstormingIdea for a potential new feature or adaption that still needs further discussionIdea for a potential new feature or adaption that still needs further discussioncode qualityTopics around code quality, e.g. refactoring, better naming of methods/classesTopics around code quality, e.g. refactoring, better naming of methods/classescomments welcomeIndicates that the creator of this issue/PR is open for early review commentsIndicates that the creator of this issue/PR is open for early review commentspriority:lowShould be quite a far way down on the agendaShould be quite a far way down on the agenda
A general review of all classes' and packages' names and structures would be useful.
For example,
AggregateRequestExecutor.javaandDataRequestExecutor.javacould be renamed toAggregationRequestExecutor.javaandExtractionRequestExecutor.java. So these classes will follow the same naming criteria used in other packages, i.e. in the packageoutput:DefaultAggregationResponse.javaandExtractionResponse.java.