-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Scala API #1
Comments
+1 |
11 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
👍 |
+1 |
+1 |
+1 |
+1 |
+1 |
+9000000000000000L (withMagicBase) |
:+1 Also please don't make Guice/JSR330 the norm - plain constructor DI is just fine thanks. |
A little bit more than just a +1... Is there are a draft already for the Scala API? I've been working myself on a CQRS/ES library (www.funcqrs.io). Some of you were probably already aware of it. If not I invite you guys to have a look on it. Although this may sound like a shameless plug for Fun.CQRS, my goal here is rather to start a discussion about the Scala API for Lagom. I've spent a lot of time in tweaking and collecting feedback from the DDD community in order to refine Fun.CQRS' API and I think the same should happen with Lagom. So, my question is: which Scala API do we want for Lagom, how does it should look like, which shape do we want it to have? |
+1 |
1 similar comment
+1 |
@rcavalcanti This seems to be a voting ticket, discussion will probably have to happen elsewhere ;-) Another consideration is that @jroper is a master troll :-D |
@rkuhn I want to see the first one to down vote it. ;-) |
-1 |
There, see what you have done … |
Well, somebody had to balance out @jamie-allen. |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
In the interest of cleaning up this issue, maybe all the folks who added “+1” or similar comments could delete them and add reactions instead? |
+1 |
1 similar comment
+1 |
ClassTag instead of Class parameter, #1
* for scaladsl-persistence and scaladsl-persistence-jdbc * factory for PersistentEntity registration * factory for ReadSide registration * components trait for compile time DI * separate traits for write and read side * split up cluster module * remove guice
* for scaladsl-persistence and scaladsl-persistence-jdbc * factory for PersistentEntity registration * factory for ReadSide registration * components trait for compile time DI * separate traits for write and read side * split up cluster module * remove guice
support for compile time dependency injection, #1
* The return type from PersistentEntityRef.ask was inferred to Future[Nothing] * Add type member in ReplyType and use that in ask * To make the CommandContext.reply method use the right type I changed the definition of the command handlers to be per command class, which also has several other benefits: * no need to pass the command as parameter to reply * defining handler per class is more natural than chaining one single partial function * easier to read (understand) the command handler definitions when the types are enforced
infer right reply type in entityRef.ask, #1
use ClassTag in PersistentEntityRegistry.refFor, #1
Hi! |
The Scala API is nearing complete and we hope to release a milestone in the coming weeks. We haven't yet moved to Scala 2.12, on our critical path is getting a release of Play that is built against 2.12. They haven't yet built against Scala 2.12, but they are working on it here: playframework/playframework#6691 Once they do that, if they backport that to Play 2.5, then it should be no problems, otherwise we'll need to wait until Play 2.6 is released. |
Update: Once #302 is merged, the Scala API will be mostly usable, the only major feature gap is pubsub which I'm working on right now and should be finished tomorrow. Our plan is to release a milestone in the first week of December (next week). We did want to release the final by the end of the year, but I don't think that's a realistic amount of time, especially given that community feedback would be valuable and it will probably take longer than that to get meaningful feedback from the community, so our current plan is to release the final by the end of January. |
Looking forward to it! |
I am looking forward it too!!!!:)) |
looking forward |
We've just cut Lagom 1.3.0-M1 as a preview release of the Scala API: http://www.lagomframework.com/blog/lagom-scala-api-preview.html We would appreciate evaluators to check it out, and give us feedback. Note that there are things about this API that will change before we cut the final (due at the end of January), so we don't recommend using it in a production system yet. |
Looks awesome so far. I'm building two new services with it and will probably convert a few more soon. I assume that com.lightbend.lagom.scaladsl.testkit.ServiceTest is one of those testkit API's that isn't finished yet. |
It is finished, you can find it if you build master from source, it's just not in the 1.3.0-M1 release. |
The Lagom Scala API, including documentation, is now complete. See http://www.lagomframework.com/blog/lagom-1-3-RC1.html for details. |
Lagom needs a Scala API.
The text was updated successfully, but these errors were encountered: