feat: add in support for async paths #62
Merged
Conversation
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
RubenHalman
approved these changes
Feb 22, 2024
Member
RubenHalman
left a comment
RubenHalman
left a comment
There was a problem hiding this comment.
Just wow! Thank you so much for this high quality contribution. I will try to publish this ASAPa
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.
Background
Asynchronous paths aren't being considered when parsing for FlowNodes.
Unlike Synchronous paths where the start element immediately has
connectors; async paths branch off ofscheduledPathsFrom my investigation there are 2 flavors of scheduledPaths