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.
Summary
This PR fixes a bug where the displayed webhook URL would change after a webhook trigger was created and its data loaded from the API. Previously, the URL was initially computed using
blockIdas a fallback, but would reactively update if thetriggerPath(from the loaded webhook data) differed. This caused instability and broke external integrations.The fix ensures the webhook URL is always consistently computed using the
blockId, making it stable from creation and preventing unexpected changes.Fixes # (issue) - [Bug] I added a slack trigger from scratch. At some point, the webhook URL changed.
Type of Change
Testing
The changes involve simplifying the webhook URL computation to always use
blockId. Reviewers should focus on ensuring that this consistent use ofblockIdfor the webhook URL display aligns with how webhooks are created and handled in the backend, and that no other components rely on thetriggerPathfor URL display.Checklist
Screenshots/Videos