Skip to content
This repository was archived by the owner on Jun 29, 2026. It is now read-only.

1.9.0

Choose a tag to compare

View all tags
@armiol armiol released this 20 May 15:05
· 8 commits to v1 since this release
v1.9.0
f41a878
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This release is a part of Spine 1.9.0.

Notable changes:

  • Bulk keep-up and cancellation requests for subscriptions (#193).

This feature was previously a hot-update for Spine 1.7.4. Now, the functionality is ported to v1 branch.

  • HttpClient customisation (#194).

It is now possible to customise HttpClient for each type of requests (sending commands, queries, or interacting with subscriptions).

In particular, end-users are now able to set HTTP headers, request mode, or customise how the original Proto message is transformed for transmission over the wire.

Additionally, a new HttpResponseHandler routine has been extracted from the existing code to allow its customisation for end-users.
It is responsible for transforming the raw response content into JS objects. The default implementation — what we used to have in previous versions as a hard-coded behaviour — expects the server-side to return a JSON string, and parses it into a JS object.

  • Immediate subscription cancellation (#195).

Calling unsubscribe for any subscription now leads to an immediate cancellation on both client- and server-side. Previously, all such cancellations were only processed during the next "keep-up" propagation.

Client now allows cancelling all known subscription via cancelAllSubscriptions() no-args call. Its invocation leads to sending the bulk cancellation request to server-side, as well as shutting down the client-level subscriptions. Such an API is useful in case end-users choose to log out from the application.

  • Observing Entity deletions at client-side (#197).

Previously itemRemoved callback for subscriptions was not functioning properly. Now, it is invoked whenever a target Entity becomes archived or deleted.

  • Updated third-party dependencies:

    • Firebase Admin SDK (server-side) ~> 9.1.1,
    • Firebase JS SDK (client-side) ~> 9.16.0,
    • Guava ~> 31.1-jre,
    • Google's repackaged Apache HTTP Client is now at version 2 (v1 is now deprecated) ~> 1.42.2.
Assets 2
Loading