Matthias Kurz
Matthias Kurz
I opened a pull request which addresses some of the newline complains. See #169
#169 is merged, that should make the newline behaviour a *bit* better. However for twirl expressions like `if`, `for`, etc. I think a solution *could* be to remove that lines...
@SethTisue As you probably have noticed, #590 got merged.
@xuwei-k Do you can/want to help?
@xuwei-k @SethTisue did you see [these 2 comments](https://github.com/lampepfl/dotty/issues/12731#issuecomment-907134727)? Replacing F-bounds by intersection types? WDYT? Also see https://github.com/lampepfl/dotty/issues/13133 and https://github.com/lampepfl/dotty/issues/10638#issuecomment-739151145 > If you have an F-bounded type `T
@SethTisue Currently not so much time as well (coming weeks)...
Servus, my time is limited the next 3 weeks (see https://github.com/orgs/playframework/discussions/11313), however if you want to dig in and want to provide pull requests you are more than welcome to...
@fgrutsch There is [Play JSON 2.10.0-RC6](https://github.com/playframework/play-json/releases/tag/2.10.0-RC6) already which does have support for Scala 3, does that work for you for now?
Pull request to resolve this issue would be welcome.
Not sure what the original problem really is about, but just guessing, could it be that a play-slick component needs to depend on (inject) the `ApplicationEvolutions`, to make sure evolutions...