lrytz/play-scala-compile-di-with-tests — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2017-02-09
Wire controllers, routing, and services explicitly in a MyComponents class instead of using runtime dependency injection.
Catch dependency wiring mistakes at compile time before the app even runs.
Spin up a fresh app instance per test suite using custom ScalaTest helpers.
Migrate an existing Play app away from convention-based automatic dependency injection.
| lrytz/play-scala-compile-di-with-tests | cakiki/database | janikdotzel/akka-http-quickstart-scala | |
|---|---|---|---|
| Language | Scala | Scala | Scala |
| Last pushed | 2017-02-09 | 2026-03-13 | 2023-05-19 |
| Maintenance | Dormant | Maintained | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 2/5 | 2/5 |
| Audience | developer | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires understanding manual dependency wiring instead of Play's default runtime DI, which has a learning curve.
A Play Framework example showing how to wire Scala app dependencies explicitly at compile time, including how to keep that setup working with ScalaTest.
Mainly Scala. The stack also includes Scala, Play Framework, ScalaTest.
Dormant — no commits in 2+ years (last push 2017-02-09).
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.