Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support @ExportName on bean fields #366

Closed
ljacqu opened this issue Aug 27, 2023 · 0 comments
Closed

Support @ExportName on bean fields #366

ljacqu opened this issue Aug 27, 2023 · 0 comments
Milestone
1.4.1 Release

Comments

@ljacqu
Copy link
Member

ljacqu commented Aug 27, 2023 •
edited
Loading

The goal of this issue is to allow the annotation @ExportName on fields, alongside methods for now. This provides a "transitional" state for ConfigMe 2.0, where the intention is to only allow @ExportName on fields.

To do

  • Allow @ExportName on fields
  • When creating bean properties, check for @ExportName on the field, as is already done for @Comment
@ljacqu ljacqu added this to the 1.4.1 Release milestone Aug 27, 2023
ljacqu added a commit that referenced this issue Aug 27, 2023
@ljacqu
#366 Support ExportName annotation on bean fields
e8e5c68 
- ConfigMe 2.0 will only support the annotation on fields, so we support it on accessors and fields for 1.4.1 to allow for a smoother transition
@ljacqu ljacqu closed this as completed Aug 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
1.4.1 Release
Development

No branches or pull requests
1 participant
@ljacqu