Renato Cavalcanti

I think this is a good addition. Would be interested in sending a PR?

@patriknw, the link @claudio-scandura published here was to a github compare to create the PR. The PR is now create (see #424). Let's see what happens in Travis build.

That makes sense and we should have thought about it earlier. It also makes me think about shutdown ordering. I think it's a problem that it's not entirely solved in...

If we add a constraint now we will potentially break user's code and we'll have to document and communicate about it. And users will have to migrate their offset store....

@ignasi35 / @ygree, is this something we need to have on v1.0.0 or can be added later?

I think this is a good idea. That would make it independent of the kind of kill switch is in use.

https://github.com/akka/akka-persistence-r2dbc/actions/runs/8947230726/job/24578898497#step:6:981

I see your point @aludwiko. I only find it has value with pattern matching. Otherwise, is just a matter of style and not a big deal, IMO. The possibility to...

Internal. And I'm only referring to java users and concerning code-first java with Spring, not scala users. Scala users would of course prefer pattern matching, but they are not affected...

When are you registering the module? We are doing something similar in the Kotlin template and it works as expected?