Skip to content

Conversation

@realprabs
Copy link

@realprabs realprabs commented Sep 18, 2025

When a restoration identifier is not available, the replace visits were converted to advance. This PR removes that behavior and retains the original action.

Resolves #164

@realprabs
Copy link
Author

Sorry for tagging @jayohms, I am unable to add you as a reviewer. Do you foresee any issues with this?

@joemasilotti joemasilotti requested a review from jayohms October 11, 2025 20:38
@joemasilotti
Copy link
Member

I just tagged Jay to review.

@jayohms
Copy link
Contributor

jayohms commented Nov 5, 2025

While I can see how REPLACE actions are getting unintentionally rewritten, the original implementation is intended to prevent RESTORE visits when a restorationIdentifier is not present. This change removes that part of the logic so it'll have to be reworked.

@jayohms
Copy link
Contributor

jayohms commented Nov 5, 2025

@realprabs Here's an alternate solution with logic that should work correctly: #176

@realprabs
Copy link
Author

Thank you, I am closing this PR.

@realprabs realprabs closed this Nov 6, 2025
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.

Replace visits get converted to advance

3 participants