Julien Richard-Foy
Julien Richard-Foy
The fact that this is crashing is a bug right? I would expect a compilation error on `println(*(2, 3))`?
Hi, FWIW, a workaround is to use the string interpolator: ``` scala import play.twirl.api.StringInterpolation def foo[L
You can use any caching system like the one provided by Play: https://www.playframework.com/documentation/2.7.x/ScalaCache Where precisely do you want to cache? On the server’s memory? On the client’s browser cache?
Then you would have to use the Cache-Control or ETag headers, in your response.
Once the 1.6.0 will be ready I will be happy to merge a pull request implementing this. I’m not sure I’ll have time to implement it by myself.
> messages.xxx.js files should end up in the javascripts in the resources_managed folder I think it would be better if messages could still be shared between server-side and client-side. Is...
> I'm just saying where the .js versions are generated. Not that you have to move the messages.xxx files. Ok, great! > No idea bout 2.3, big changes? It seems.
It has not been implemented. You can give it a try, if you want :)
No, I don’t use sbt-release anymore.
@ploddi I think your problem is more related to #41 than this issue.