allIssuesdoesn't actually capture all issues of a driver -- it captures all issues of a run
My team has been really fond of something like this:
api ├── MyService.scala ├── domain │ └── package.scala ├── events │ └── package.scala └── commands └── package.scala
which is really organizationally nice... not sure if that's how opinionated Lagom wants to be, though.
Does it make sense to prescribe/recommend a repo structure?
I have to write a blog post about that
implfor each services
messagesdon’t know each others