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
As I understand, the next Grails version 3.3 will have support for type checked GSPs, which I think is a great feature and I can't wait to use it!
I don't know if this is possible from a technical point of view, but I think this "type checked views" idea could be even better, if it could expand throughout the whole framework and not only the view layer: My idea would be to also provide type checked references to views. Currently, views in controllers are rendered by providing a string in the render method, like render(view: 'myView'). It would be great if such calls could also be used in a type checked manner (find missing views before runtime).
I have seen something like this implemented in the Play framework: Content html = views.html.Application.index.render(customer, orders);
I don't know if this is possible, but at least for me, this would be a very useful addition.
The text was updated successfully, but these errors were encountered:
Hello
As I understand, the next Grails version 3.3 will have support for type checked GSPs, which I think is a great feature and I can't wait to use it!
I don't know if this is possible from a technical point of view, but I think this "type checked views" idea could be even better, if it could expand throughout the whole framework and not only the view layer: My idea would be to also provide type checked references to views. Currently, views in controllers are rendered by providing a string in the render method, like
render(view: 'myView')
. It would be great if such calls could also be used in a type checked manner (find missing views before runtime).I have seen something like this implemented in the Play framework:
Content html = views.html.Application.index.render(customer, orders);
I don't know if this is possible, but at least for me, this would be a very useful addition.
The text was updated successfully, but these errors were encountered: