Closed mdedetrich closed 6 months ago
@pjfanning Should I go ahead and merge this as its related to an issue you are talking about?
I'm neutral on this. The change proposed in #90 is not massively impacting but I don't mind if we change the semver setting.
I would like to see https://github.com/apache/pekko-persistence-r2dbc/issues/90 done as it implied there is a legitimate reason why it was changed to Long
. I'll merge this when I get home
@mdedetrich R2dbcExecutor is documented to be an internal class. For me, this means we can change its return types without too much fanfare.
Maybe we should work out how big the changes in https://github.com/apache/pekko-persistence-r2dbc/pull/101 will be before we decide if we need this.
So far the public API changes are only in pekko-projection-r2dbc and not in the pekko-persistence-r2dbc module - maybe we could just remove semver marker from pekko-projection-r2dbc.
Maybe we should work out how big the changes in https://github.com/apache/pekko-persistence-r2dbc/pull/101 will be before we decide if we need this.
So far the public API changes are only in pekko-projection-r2dbc and not in the pekko-persistence-r2dbc module - maybe we could just remove semver marker from pekko-projection-r2dbc.
Sure, do you want to go ahead with the PR to find out?
I removed myself as a reviewer. That was uncool @mdedetrich.
I removed myself as a reviewer. That was uncool @mdedetrich.
Apologies, this was an accident as there is another greg as part of committers.
Due to https://github.com/apache/pekko-persistence-r2dbc/issues/90