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.

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

suppression of @ConstructorProperties should use config instead. #694

Open
lombokissues opened this issue Jul 14, 2015 · 3 comments
Open

Comments

@lombokissues
Copy link

Migrated from Google Code (issue 659)

@lombokissues
Copy link
Author

👤 r.spilker   🕗 Mar 26, 2014 at 19:25 UTC

Currently disabling @ ConstructorProperties (a thing that is generally done at the project level, because in GWT, @ ConstructorProperties is not supported, and probably not in android either) is done at the annotation level as a parameter to the annotation.

Because it's project wide (and tedious, and boilerplatey, and easily forgotten, and kind of a weird option to list during auto-complete on params), it should be removed there and turned into a config key instead. Probably by updating the deprecation method (it's already deprecated) to state that the setting is going away somewhere around April 1st 2015.

@lombokissues
Copy link
Author

End of migration

@mjustin
Copy link

mjustin commented Sep 26, 2018

Isn't this implemented now?

lianhaijun pushed a commit to lianhaijun/lombok that referenced this issue May 8, 2020
- register quick fix for add SneakyThrows annotation on unhandled exceptions
- replaced for onX handler strings to class names, also added lombok.With annotation class as handled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants