Skip to content

chore: Fix implicit intent handling #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 14, 2025
Merged

Conversation

keelerm84
Copy link
Member

Synchronizers operate by building up changes using a change set builder.
This builder is primed with a server-intent, and then updated as
subsequent changes are received.

If the initial response to the synchronizer is xfer-none, we still
need to store this intent. However, the intent code should be updated to
show that we are now waiting for pending changes. Otherwise, when those
subsequent changes arrive, the code will suggest to upstream behavior
that we have no changes to process.

Synchronizers operate by building up changes using a change set builder.
This builder is primed with a server-intent, and then updated as
subsequent changes are received.

If the initial response to the synchronizer is `xfer-none`, we still
need to store this intent. However, the intent code should be updated to
show that we are now waiting for pending changes. Otherwise, when those
subsequent changes arrive, the code will suggest to upstream behavior
that we have no changes to process.
@keelerm84 keelerm84 requested a review from a team as a code owner May 13, 2025 15:20
@keelerm84 keelerm84 merged commit 48de5e3 into v7 May 14, 2025
18 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-931/implicit-intent branch May 14, 2025 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants