-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
fix: Chat triggers don't work with the new partial execution flow #11952
Merged
despairblue
merged 10 commits into
master
from
pay-2166-chat-triggers-dont-work-with-the-new-partial-execution-flow-try-2
Dec 4, 2024
Merged
Changes from 9 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
60d81e2
refactor(core): Use an options object for `needsWebhook` instead of p…
despairblue df26d52
refactor(core): group tests in desribe block
despairblue a78d8ce
fix: Fix chat trigger with partial executions v2 by allowing the FE t…
despairblue 4dbc563
add test
despairblue b4dc389
add clarifying comment
despairblue 02a4aa1
destructure options
despairblue c50ffbe
fix comment
despairblue 924294b
rename preferredTrigger to triggerToStartFrom
despairblue b27590f
don't use runData from FE
despairblue f68c0d7
undo change that was committed by accident
despairblue File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be an
else if
with the next check?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't follow.
This check is removing all but one webhook from the list if the preferred trigger was passed.
The next check is checking if the the list contains at least one trigger that is restartable (I think 🤔 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the question is, can it ever happen that a trigger to start triggers the restartable check? What exactly is
w.webhookDescription.restartWebhook
?But if not worth it let's leave it :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know either tbh. Jan added this here: 5a179cd#diff-b386248ff00977749c873ed85821c241b773e9740d7e7adf94e05b73b350ed74
Which is a huge commit.
It seems this is for the Form, Wait, Slack and Gmail nodes.
I guess that would be fine still. I'm assuming this is to not listen for webhook for workflows that have been put to into waiting?
Which means you can't actually pick them as a trigger to start from.
At least for the the wait and form nodes this is only interesting for workflows that wait, probably for slack too, e.g. if you render a dialog and wait for the user to click a button. I'm not sure why the gmail node offers this though.
I guess this can be left until the split button is implemented.
cc @cstuncsik @CharlieKolb