You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the sample spring application https://github.com/xmlet/spring-petclinic already integrated with HtmlFlow, enhance it with a ViewResolver. This resolver must obey with the strongly typed approach of HtmlFlow and avoid String to map views.
The text was updated successfully, but these errors were encountered:
I think that we do not need the ViewResolver when routes return a String corresponding to the path of a view. Others need that because their views are text files in a resource folder. But HtmlFlow views are Java types that take advantage of static compilation.
Yet, there are some use cases where routes return directly a ModelAndView or even an object T of model and the view is inferred from the path request. For those cases the ViewResolver may be useful.
Regarding the sample spring application https://github.com/xmlet/spring-petclinic already integrated with HtmlFlow, enhance it with a ViewResolver. This resolver must obey with the strongly typed approach of HtmlFlow and avoid String to map views.
The text was updated successfully, but these errors were encountered: