-
Notifications
You must be signed in to change notification settings - Fork 30
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
Response types have optional keys #214
Labels
Type: Bug
Something isn't working as documented, or is being fixed
typescript
Relevant to TypeScript users only
Projects
Comments
gr2m
added
the
Type: Support
Any questions, information, or general needs around the SDK or GitHub APIs
label
Dec 2, 2020
ghost
added this to Support
in JS
Dec 2, 2020
gr2m
added
Type: Bug
Something isn't working as documented, or is being fixed
typescript
Relevant to TypeScript users only
and removed
Type: Support
Any questions, information, or general needs around the SDK or GitHub APIs
labels
Dec 2, 2020
ghost
moved this from Support
to Bugs
in JS
Dec 2, 2020
We could selectively apply the fix to only these routes which currently lack a
See also: github/rest-api-description#109 |
gr2m
added a commit
that referenced
this issue
Dec 2, 2020
gr2m
added a commit
that referenced
this issue
Dec 2, 2020
🎉 This issue has been resolved in version 6.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
gr2m
added a commit
that referenced
this issue
Jun 29, 2021
gr2m
added a commit
that referenced
this issue
Jun 29, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Type: Bug
Something isn't working as documented, or is being fixed
typescript
Relevant to TypeScript users only
This is a problem with the Official OpenAPI specs, see e.g.
components/schemas/installation-token
is missing"required"
key github/rest-api-description#106Many response types seem to be affected, not all however. E.g.
Endpoints["GET /repos/{owner}/{repo}"]["response"]["data"]
has the correct types.Until this problem is resolved on GitHub's side, we could recursively make all response properties non-optional
The text was updated successfully, but these errors were encountered: