Update CLAUDE.md - Feature Class Structure and Main Class Explanations #468
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.
This pull request updates the
CLAUDE.mddocumentation to provide clearer, more structured explanations of the main classes and architecture for each major plugin feature.The changes include:
Separation of Plugin Overview and Feature Details: The document now clearly distinguishes between the overall plugin architecture and the detailed explanations of each feature.
New Section:
"Main Classes of Each Feature": Added a dedicated section that describes the main classes for each feature (Actions, Inspections, Refactoring, Reference Resolution, Documentation, Formatter, etc.), with consistent heading levels and categorization.
Detailed Class Descriptions:
For each feature, the main classes are listed with concise explanations of their roles and processing targets. For example, the Refactoring section now distinguishes between processors for DAO class renaming, DAO method renaming, and package renaming.
Class Naming Conventions:
Each feature section now explicitly states the naming conventions for its main classes (e.g., suffixes like Processor, Reference, DocumentationProvider, etc.).
Reduced Heading Nesting:
The document structure has been flattened for better readability, with all feature details grouped under a single "Main Classes of Each Feature" section.