feat: promise id lineage separator '.' -> ':' - #462
Open
Tomperez98 wants to merge 1 commit into
Open
Conversation
Only the promiseId<->lineage boundary uses ':'; lineage segments keep '.' (foo.1 -> foo:1, foo.1.1 -> foo:1.1).
Tomperez98
force-pushed
the
tomas/id-formatting
branch
from
August 10, 2026 23:05
ae8a7fc to
d8d6637
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adopts the
<promiseId>:<lineage>id convention. A single:separates thepromiseId (the lineage origin) from the lineage; within the lineage the
separator stays
.. So:foo.1->foo:1(promiseIdfoo, lineage1)foo.1.1->foo:1.1(promiseIdfoo, lineage1.1)What changed:
(
id == origin) uses:; deeper segments use.. Detached ids mint{prefix}:d{hash}(their first lineage segment off the fixed prefix).:(NATS routing, where applicable).The schedule promise-id template keeps
.({{.id}}.{{.timestamp}}): ascheduled promise is a self-rooted promiseId, not a lineage. The app id prefix
(
RESONATE_PREFIX,:-joined) is unchanged. Companion server-side changeshandle the matching validation and origin rules.