Play 2.4.0 support follow-up

[Oleg Ilyenko]

Hi everybody,

Play 2.4.0-RC1 is out now and I wanted to give a small update on scaldi-play support for it. It took quite a few iterations, but scaldi-play is up-to-date with the current state of DI mechanism of play 2.4.0-RC1. 

The development is still taking place int it in the play-2.4 branch and latest version is 0.5-play-2.4.0-RC1-8 which integrates with play 2.4.0-RC1:

libraryDependencies ++= Seq(
  "org.scaldi" %% "scaldi-play" % "0.5-play-2.4.0-RC1-8"
)

Just a reminder - you can find an example of it's usage in this small project:

https://github.com/OlegIlyenko/scaldi-play-example

In order to use Scaldi as a DI provider of play you need to define application loader in the application.conf:

play.application.loader = scaldi.play.ScaldiApplicationLoader

I think the biggest change since last update is testing API. So far I kept it semantically very close to the Guice API, which Play team intend to provide out-of-the-box in 2.4.0. They already have some documentation for it:

https://www.playframework.com/documentation/2.4.x/ScalaTestingWithGuice

You can use the same approach to testing, just replace `Guice` with `Scaldi` :)

I also would like to thank all people who are helped me and provided valuable feedback! It was super helpful and you guys are awesome!!

The integration with play 2.4.0 is still in progress, so you can expect API changes, but I have a feeling that it already in taking a good shape, even though some polish and cleanup is still needed.

As always, I would really appreciate your feedback!

Cheers,

Oleg