fix: passing data to interrupting boundary escalation event#2
Merged
Conversation
sondregj
marked this pull request as ready for review
June 5, 2025 08:29
Anders-eide-stacc
approved these changes
Jun 5, 2025
Anders-eide-stacc
left a comment
Anders-eide-stacc
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, but would like to know what scope is returned by getFlowScope, to know if there is a possible risk of collisions
sondregj
force-pushed
the
fixinterruptingescalationevent
branch
from
June 5, 2025 12:52
ed8d0f7 to
01fab89
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
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.
No description provided.