2.6.0 assets migration ... put it into JavaContextComponents ? [JAVA]

[Dominik Dorn]

I'm just migrating the assets-code in my current project and 

noticed that its quite a pain to get them from their static usage

to the injected one. 
I was wondering if it wouldn't be better to either

a) put it into JavaContextComponents as well

or 

b) provide a easy way for users to create own things 

that then are implicitly available in their templates (this might be 

already possible, but I couldn't find information about it)

What do you think? 

Cheers,
Dominik

--

Dominik Dorn
http://dominikdorn.com | http://twitter.com/domdorn
XING: https://www.xing.com/profile/Dominik_Dorn
LINKEDIN: http://at.linkedin.com/pub/dominik-dorn/66/b42/bb1/

[Will Sargent]

Can you provide some example code, showing the before and after and how it's difficult to migrate?

There are injectable templates, and you can do fun stuff by providing implicits into templates using templateImports in build.sbt.  Would something like that be a good way to cross cut imports?

--

Will Sargent

Engineer, Lightbend, Inc.

will.s...@lightbend.com

--
You received this message because you are subscribed to the Google Groups "Play framework dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framework-dev+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.