Add spec for capability for unknown message type in webhook parsing #430
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
mokuzon
force-pushed
the
release_v2/specs/webhook/unknown-message-type
branch
from
7a3aaa2 to
78c1395
Compare
mokuzon
force-pushed
the
release_v2/specs/webhook/unknown-message-type
branch
from
78c1395 to
8e8c554
Compare
Yang-33
approved these changes
Apr 1, 2025
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.
Add a spec to make sure that parsing does not fail if there is a
typeundefined in the SDK inside the webhook when the SDK is not up-to-date.The webhook type itself is already tested, and this PR further tests it with an internally nested message type.