|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Related
|
|
|
|
This issue is related to:
|
|
|
GRAILS-3591 bindData has the option to explictly "include" and "exlude" fields from binding, however this not documeted
|
|
|
|
|
|
|
This change needs to be made because the "excludes" behaviour is insecure as domain classes change over time, but even more annoying, is that it is much harder to work out what to exclude than what to include, as you can look at the form and easily tell what to include!
Hey, I wrote the original so I can complain about it too 
|
|
Description
|
This change needs to be made because the "excludes" behaviour is insecure as domain classes change over time, but even more annoying, is that it is much harder to work out what to exclude than what to include, as you can look at the form and easily tell what to include!
Hey, I wrote the original so I can complain about it too |
Show » |
|
Improvement
Resolved
Critical
Refactor bindData to remove 3 param form with "excludes" list and replace with 3 param form that takes Map as 3rd param with "includes" and "excludes" support
made the changes you suggested along with matching tests.
cheers
Lee