Skip to content

Add ACTIVATE ProtocolMessage Action#280

Merged
VeskeR merged 1 commit intomainfrom
add-activate-action
Mar 25, 2025
Merged

Add ACTIVATE ProtocolMessage Action#280
VeskeR merged 1 commit intomainfrom
add-activate-action

Conversation

@VeskeR
Copy link
Contributor

@VeskeR VeskeR commented Mar 13, 2025

TR2 reads as follows:

ProtocolMessage Action enum has the following values in order from zero:

and then lists the enums values.
My intention is to preserve the wording of the TR2 and just add the new actions for LiveObjects: STATE and STATE_SYNC (#279).
And in order to do that, we need to first add the ACTIVATE action that is currently missing. Realtime enum: https://github.com/ably/realtime/blob/2fcbe71939df11794e31b29536accf076acdabec/protocol/common.proto#L139, and also added to ably-js even though not part of the spec: https://github.com/ably/ably-js/blob/a7d8181d62fcb2375cdaef3e86eb61c2fa349070/src/common/lib/types/protocolmessagecommon.ts#L23

@SimonWoolf @mschristensen Could you please briefly describe the ACTIVATE action so I can write a description for it for the protocol page?

@VeskeR VeskeR force-pushed the add-activate-action branch from c5de3cc to d44ca77 Compare March 13, 2025 10:37
@github-actions github-actions bot temporarily deployed to staging/pull/280 March 13, 2025 10:38 Inactive
@VeskeR VeskeR changed the title Add ACTIVATE ProtocolMessage Action Add ACTIVATE ProtocolMessage Action Mar 13, 2025
@SimonWoolf
Copy link
Member

Could you please briefly describe the ACTIVATE action so I can write a description for it for the protocol page

it's deprecated, no-one should be implementing it now, so no reason to document. (it existed just to support ably-js transport upgrading, before v2 removed transport upgrading). I recommend "(reserved for a deprecated use)" or something

@VeskeR VeskeR force-pushed the add-activate-action branch from d44ca77 to 30bb437 Compare March 19, 2025 08:09
@github-actions github-actions bot temporarily deployed to staging/pull/280 March 19, 2025 08:10 Inactive
@VeskeR VeskeR marked this pull request as ready for review March 19, 2025 08:10
@VeskeR VeskeR force-pushed the add-activate-action branch from 30bb437 to c96efc9 Compare March 19, 2025 08:10
@github-actions github-actions bot temporarily deployed to staging/pull/280 March 19, 2025 08:11 Inactive
@VeskeR VeskeR force-pushed the add-activate-action branch from c96efc9 to 436309e Compare March 25, 2025 08:30
@VeskeR VeskeR merged commit 1af91d3 into main Mar 25, 2025
2 checks passed
@VeskeR VeskeR deleted the add-activate-action branch March 25, 2025 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants