Avoid throwing error if interaction does not exist#602
Merged
philipwalton merged 6 commits intov5from Mar 26, 2025
Merged
Conversation
Co-authored-by: Philip Walton <philipwalton@users.noreply.github.com>
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
2 participants
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.
Fixes a bug introduced in #585.
After 10 interactions, it's possible, the next one interaction has an
interactionIdbut is not longer than the smallest one.In this case we should not run
_onAfterProcessingInteraction(and specificallysaveInteractionTargetwhich assumes an interaction will be passed).Also includes a rename of
_onAfterProcessingInteractionto the more accurate_onAfterProcessingINPCandidate