-
Notifications
You must be signed in to change notification settings - Fork 54
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
Unable to handle model properties that contain dots (.
)
#362
Comments
Hi @checketts, thanks for reporting and, ooof, this is wild. I'm not a Spring user, but modifying Spring keys to match jte parameter name syntax is asking for trouble. For instance, once Spring starts having keys with underscores that might collide with the hacked keys. I'm not sure, but maybe there could be other ways to access those things into the jte templates? Input from real Spring - jte users would be very welcome here :-) |
The way I've worked around it in my code is to create a For JTE, when populating a For example (in a
Then if there is a key with underscores that would match, it would be used first, and if not, then check for a key with periods? |
No, I would rather not introduce this kind of magic to jte. It will add a performance overhead for every template invocation through maps. It also obfuscates constants (e.g. in your example a project wide search will not find Adding a utility method to the spring lib sounds like a much better API for this problem. |
With Spring validation, when a form entry has an error Spring adds a
BindingResult
to the model with the key similar toorg.springframework.validation.BindingResult.myEntry
. However there isn't a way to reference the model entry via a@param
Since there are dots in the variable name that isn't allowed.
Would a PR for the Spring integration that changes the dots for underscores be welcome?
I'm looking to see if there are other options as well...
The text was updated successfully, but these errors were encountered: