-
Notifications
You must be signed in to change notification settings - Fork 364
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
Expose some properties as Enums #578
Comments
Even if an Enum is used, if a property name will change, it's Enum name will change as well. The properties are already exposed as constants you can reference programmatically, so you don't need to use the String values in the Java based Spring configuration. |
Thanks for your quick answer. I understand your point regarding to the Enum name.
|
Yes, that's right. I was under the impression that it's possible to use the If you this it's useful, you could try to provide a Pull Request that adds support for this feature. |
We are using
hypersistence-utils
in our applications, but we are not using thehibernate.properties
explicitly. Instead, we are customizing the object mapper via Spring@Configuration
, extendingHibernatePropertiesCustomizer
.It would be very useful if we do not have to depend on string changes on both sides, I mean, if in the future you decide to change
hypersistence.utils.jackson.object.mapper
property name to something else, developers would also have to change it.I would like to suggest exposing those properties as enums.
The text was updated successfully, but these errors were encountered: