-
Notifications
You must be signed in to change notification settings - Fork 235
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
[Schema Inaccuracy / Question] owner
in #/components/schemas/repo-search-result-item/
and #/components/schemas/repository
is nullable
#440
Comments
To add to that, this must have been changed in the last few days. I sadly cannot figure out in which commit since the Git diff (on GitHub) does not seem to work properly with these raw files (and blame does not work at all). |
The same problem exists in repository:
title: Repository
description: A git repository
type: object
properties:
id:
description: Unique identifier of the repository
example: 42
type: integer
node_id:
type: string
example: MDEwOlJlcG9zaXRvcnkxMjk2MjY5
# ...
owner:
nullable: true
allOf:
- "$ref": "#/components/schemas/simple-user"
# ... |
owner
in #/components/schemas/repo-search-result-item/
is nullableowner
in #/components/schemas/repo-search-result-item/
and #/components/schemas/repository
is nullable
Does not appear possible to be null on both repository and minimal-repository. Fix is incoming. It appears to have been this way since the launch of this description however. Thanks folks. |
Thank you so much @xuorig. It confuses me, however, because my CI started failing exactly with the Dependabot PR that updated the types at one point. I was also able to manually confirm this (my code had correct types with non-nullable |
Confirmed that it's fixed now, thanks @xuorig @creativecreatorormaybenot |
@creativecreatorormaybenot there is another problem with the OpenAPI spec which can result in the |
@gr2m thank you so much! |
Schema Inaccuracy
Update: See comment below for
#/components/schemas/repository
Expected
I didn't expect it to be nullable. If it is for a good reason, can we add add a description explaining what the reason is?
ref octokit/types.ts#338
The text was updated successfully, but these errors were encountered: