feat: Relay webhook events to localhost + UI #283
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For development and demos, there’s a gap in the end-to-end workflow for interacting webhooks event. A common issue when developing a webhook endpoint is that you have to deploy it to a public URL in order to receive events to test it. Having to deploy every change in order to test it is not an ideal developer experience and for some, there may not be immediate available public URL from their to use without relying on a third party software.
We aim to extend the utility to allow testing of the webhooks without relying on a third party software (e.g. https://webhook.site/ and instead create an on-the-fly publicly accessible URL for use when testing.