fix(types): mark type parameters as optional #1101
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
Some types which end-users could be using, declare the type parameters as requried, when in fact they are entirely optional. This arises when users try to use the event handler code on it's own
wolfy1339
added
the
Type: Bug
|
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
1 task
oscard0m
approved these changes
Feb 24, 2025
|
🎉 This PR is included in version 13.7.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Some types which end-users could be using, declare the type parameters as requried, when in fact they are entirely optional.
This arises when users try to use the event handler code on it's own
Resolves #ISSUE_NUMBER
Before the change?
After the change?
unknownThis change shouldn't introduce any noticeable behaviour changes for users who use the default
WebhooksclassPull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!