Releases: replicant4j/replicant
Releases · replicant4j/replicant
v6.137
v6.136
Changes in this release:
- Update the
org.realityforge.javax.annotation
artifact to version1.1.1
. - When an entity is removed from replicant then forcibly unsubscribe from any subscriptions where that entity is the root instance. Historically this would be cleaned up in removeOrphanedSubscriptions but may take a brief time to do so. This change avoids potential crashes when downstream code directly observes replicant Subscription objects and attempts to access instance root.
v6.135
Changes in this release:
- Add hook method
AbstractReplicantEndpoint.onSessionOpen(...)
v6.134
Changes in this release:
- Update the
org.realityforge.react4j
artifacts to version0.196
. - Update the
org.realityforge.arez
artifacts to version0.209
. - Add some documentation for
AreaOfInterest.Status
values. - Add some utility methods
AreOfInterest.Status.shouldDataBePresent()
andAreOfInterest.Status.isErrorState()
v6.133
Changes in this release:
- Fix nullability annotation on
EntityChangeEmitter.attributeChanged#value
- Update the
org.realityforge.guiceyloops
artifact to version0.113
. - Update the
org.realityforge.react4j
artifacts to version0.194
. - Update the
org.realityforge.arez
artifacts to version0.208
. - Move to GWT version
2.10.0
.
v6.132
Changes in this release:
- Update the
org.realityforge.react4j
artifacts to version0.193
. - Update the
org.realityforge.arez
artifacts to version0.207
.
v6.131
Changes in this release:
- Update the
org.realityforge.react4j
artifacts to version0.192
. - Update the
org.realityforge.arez
artifacts to version0.206
. - Remove the
org.realityforge.replicant.server.graphql
package and related infrastructure. - Upgrade to require JDK 17 as a baseline.
v6.130
Changes in this release:
- Explicitly catch SecurityException when processing WebSocket messages to avoid emitting stack traces in the logs.
v6.129
Changes in this release:
- Introduce the concept of the
FATAL_ERROR
state for connectors where no attempts to reconnect accor. This state is set when we get an error message that starts with the string"java.lang.SecurityException:"
under the assumption that a user will not recover until given appropriate permissions.
v6.128
Changes in this release:
- Stop passing the filter from the source graph to a target graph during a traversal of an internal subscription graph link if the target graph expects no filter parameter. Otherwise, when a non-bulk subscription occurs, the filter is added to target and will not match the same graph when multiple graph links points at the same target graph and the client will crash with an error like: "Attempt to update channel 1.45.X but channel does not allow dynamic updates of filter and channel has not been explicitly subscribed.".