by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Albaro Pereyra
@AlbaroPereyra
The problem with that is that then it becomes like any Perl script, “there is more than way to do it”. I believe this needs to be officially supported to allow module developers the opportunity to make multi-site decisions. I know I should not compare the Play Framework to but, both WordPress and Drupal support multi-site, they have similar yet distinct module support etc. for multi-site.
nafg
@nafg
I would be more than happy if there was built in support
Arnout Engelen
@raboof
I see sbt-twirl 1.5.0 was just released - is it safe to upgrade or might that conflict with older versions of play?
Thibault Duplessis
@ornicar
Many thanks to all playframework contributors <3 You're doing an awesome job!
N.S. Cutler
@godenji
@ornicar agreed, now upgrade Lichess to play 2.7 :sweat_smile:
nafg
@nafg
2.8.0 is on maven but I don't see it mentioned anywhere?
Albaro Pereyra
@AlbaroPereyra
2.8 is the latest version; https://www.playframework.com/documentation/2.8.x/Home
nafg
@nafg
Why is Cookies deprecated? https://github.com/playframework/playframework/blob/2.8.x/core/play/src/main/scala/play/api/mvc/Cookie.scala#L154
There doesn't seem to be a replacement for Cookies.apply
https://github.com/playframework/playframework/pull/9215#issuecomment-566209704
Thibault Duplessis
@ornicar
@godenji I've actually upgraded to play 2.8 and it's deployed to production
N.S. Cutler
@godenji
@ornicar great, Lichess is fantastic; that it runs on Play/Scala makes it even better :)
gavinbaumanis
@gavinbaumanis

Hi Everyone, Is there any documentation about the features that are expected to be in future releases?
(I am specifically after : "When will forms allow > 22 fields)
But from an interest perspective - I'm keen to know of what's planned.

Is there anything? Is it "public"? - I can't find anything in Github of the playframework web page - Thanks.

gavinbaumanis
@gavinbaumanis

I attempted to create a local copy of the playframework documentation (to test a PR) with;
sbt publishLocal, using openjdk 13 and it failed;

Using openJDK 8 (202) compiles successfully

There is an issue logged already;
JNA error running ~run #9999

Is the same thing - or should I log another issue?

Matthias Kurz
@mkurz
@gavinbaumanis I guess #9999 is actually the problem you experience since you are building from current HEAD. So no need to open a new issue. However I do not recommend do build Play with jdk 13 because it's not officially supported. jdk 8 is officially supported and jdk 11 should work without any problems as well (we do run tests with jdk 11 and everything works fine). Also be aware that Play probably will never support non-LTS jdk releases, (jdk 17 being next LTS after jdk 11)
About the roadmap: AFAIK a public roadmap should be published soon by the Play team.
gavinbaumanis
@gavinbaumanis
@mkurz : Thanks very much. In that case it would be good to have this information in the documentation.
It might be there already, but it certainly isn't on the page that describes how to build the documentation - and I hazard a guess (famous last words !!) - that is likely not in all places that compiling XXX from source code is mentioned. I am happy to raise an issue and make a PR for the documentation changes I can find.
gavinbaumanis
@gavinbaumanis
After what seems like 100 commits I finally managed to get my DOCUMENTATION PR to pass the tests on TravisCI.
Is there a way I can run these test locally, before I commit - so I don't end up using Travis as a test platform?
Will Sargent
@wsargent
@nafg 2.8.1 is out now and fixes the cookie issue
https://github.com/playframework/playframework/releases/tag/2.8.1
J T
@tianjianfeng
Hi, In play 2.8, WithApplication is missing in play.api.test. Any ideas why?
Igmar Palsenberg
@igmar
Isn't that play.test.WithApplication ?
Arnout Engelen
@raboof
any mergify experts in the room? it seems confused in playframework/playframework#10142
Ignasi Marimon-Clos
@ignasi35
Let me see (not an expert though…)
Ignasi Marimon-Clos
@ignasi35
Really strange. I’ve raised Mergifyio/mergify-engine#849 with mergify.
N.S. Cutler
@godenji
Looking ahead, when can we expect to see early release builds for Dotty/Scala 3.0?
First RC is slated for the end of the year, but there will be many milestone builds prior to that; would be great to be able to start porting existing Scala 2/Play projects at that time.
gavinbaumanis
@gavinbaumanis
Hi there how do I contribute an example application?
I have created a play application that uses “just” JDBC - no Slick / doobie and also has nested classes to deal with.
https://github.com/gavinbaumanis/play-scala-jdbc
11 replies
kerr
@hepin1989
https://www.reddit.com/r/scala/comments/g71bmi/scala_what_are_the_drawback_or_why_should_i_not/
gavinbaumanis
@gavinbaumanis
Hi there;
is there any news for;
  • be allowance for greater than 22 fields?
  • Upgrade Akka
Arnout Engelen
@raboof
@gavinbaumanis since Akka provides binary compatibility, typically you should be able to use a newer Akka version than the one Play is requiring in your project.
@gavinbaumanis playframework master is already on 2.6.4, but I think that will become play 2.9, for which we don't have release plans yet at this point AFAIK
anyone feel like a quick review? playframework/scalatestplus-play#253 :)
gavinbaumanis
@gavinbaumanis
@raboof THanks.
Arnout Engelen
@raboof

anyone feel like a quick review? playframework/scalatestplus-play#253 :)

already done, thanks ;)

Arnout Engelen
@raboof
how do we version scalatestplus-play? should https://github.com/playframework/scalatestplus-play/compare/5.0.0...master be 5.0.1, 5.1.0 or 6.0.0?
Renato Cavalcanti
@renatocaval
it depends if it has breaking changes
5.0. 1 for patch but fixes, not the case here
5.1.0 for releases containing breaking changes
I think that's the case this time considering the fact that there are mima exclusions in the diff
Arnout Engelen
@raboof
yeah I think the main thing is the scalatest 3.1.1 update
5.1.0 then?
Renato Cavalcanti
@renatocaval
yep
in the past, we use to open a new branch each time we had a new major release
that's why there is a 5.0.x branch
this time, I think we can keep going with master
until the point we need to make a 5.1.x branch
since is a project with low change rate, I think we can pretty much stay on master. Until the next breaking change coming from ScalaTest
or Play, but there is nothing schedule in Play that could potentially break it, so we are pretty much safe
Ignasi Marimon-Clos
@ignasi35
Hi all, I’ll start a release of Play 2.8.2