[freemarker] improve ftl marcos support especially for handling forms #1380
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This PR will introduce a new freemarker template
spring-form.ftlfor proper form handling similar to the spring tag library and in addition it improves some of the existing message macros.spring-form.ftl
Here is a quick example of how the new form macros work.
Most of the marcos are similar to the existing elements in the spring tag library. They also cover the type conversion via
PropertyEditorto parse and format property values in the same way as the JSP tag library.spring.ftl
Both macros now support optional parameters so there is now need to use the other marcos
messageText,messageArgsText,themeText,themeArgsTextanymore. I've marked them deprecated, but let me know if we should remove them.This PR is currently WIP, because the test cases fail and need some more love. Before I spent more time in this, let me know if this PR might be interesting and will be merged if everything is fine.