Builder Configuration: possiblity to configure specific behaviour - #100
Merged
Merged
Conversation
…essModifiers in Annotations
… read from Annotation-Options
…nd adding an entry in README.md
…tation of configuration-chain
…ntain basic value-setting functionality
…g test to check for method signatures)
…) and adepting test
… which needs to be compiled before)
…to have a full compare of the result
…ces should be removed when reading the configuration
…entation by linking to it
…always in same ordering
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



Summary
Implemented a comprehensive, multi-layered configuration system for the Simple Builders annotation processor, enabling fine-grained control over builder generation with support for project-wide defaults, reusable templates, and per-class customization.
Problem Statement
The builder generator lacked flexibility to adapt to different project requirements, functionality needed:
Solution - Architecture
Implemented a 4-layer priority system for configuration resolution:
closes #38