Standardize @Retention usage in Lombok annotationsfix: Standardize @Retention usage in annotations #3678
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
This pull request standardizes the usage of the @retention annotation across Lombok's annotations. Specifically, it changes the usage in the @builder annotation from
@Retention(SOURCE)
to@Retention(RetentionPolicy.SOURCE)
.Reason for Change
The other annotations in the Lombok project, such as @Getter and @Setter, use
@Retention(RetentionPolicy.SOURCE)
. For the sake of consistency and readability, this change ensures that all annotations follow the same convention.Changes Made
@Retention(SOURCE)
to@Retention(RetentionPolicy.SOURCE)
in the @builder annotation.Impact
This change does not affect the functionality of the annotations but improves the consistency and maintainability of the codebase.
Verification
No additional tests are needed as this change only affects the annotation declaration style.
Please review and let me know if there are any concerns or further changes needed.
Thank you!