Skip to content
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

support property retry events for extension-specific properties #1083

Merged
merged 2 commits into from
Feb 1, 2025

Conversation

jdknight
Copy link
Member

@jdknight jdknight commented Feb 1, 2025

This extension will update page properties under a get-then-update process, where a retry attempt will be made to help deal with conflict scenarios. This only applied to Confluence-specific properties and not this extension's custom property (e.g. used for page hash tracking).

This commit is updated the implementation to perform the get-then-update with retries for all property submissions, in attempt to prevent odd publish scenarios for users.

This extension will update page properties under a get-then-update
process, where a retry attempt will be made to help deal with conflict
scenarios. This only applied to Confluence-specific properties and not
this extension's custom property (e.g. used for page hash tracking).

This commit is updated the implementation to perform the get-then-update
with retries for all property submissions, in attempt to prevent odd
publish scenarios for users.

Signed-off-by: James Knight <git@jdknight.me>
A new change [1] results in at least two property fetch events on a page
update. Updating the expected results on some unit tests to indicate the
expected communication events.

[1]: e715ed8

Signed-off-by: James Knight <git@jdknight.me>
@jdknight jdknight merged commit f283001 into main Feb 1, 2025
29 checks passed
@jdknight jdknight deleted the support-property-retry-on-cb-extension-prop branch February 1, 2025 07:28
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.

1 participant