Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Schema Inaccuracy] issue/pr response fields marked as required nullable unnecessarily (?)

Open
#3,501 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Locate the OpenAPI schema definitions for issue and pull-request responses, then inspect the assignees, requested_reviewers, and requested_teams fields. Confirm their observed response shapes and update the required/nullable declarations consistently; the schema should represent these fields as empty arrays rather than nullable values where appropriate.

Written by the indexing model from the issue text.

Description

feature fundamentals-and-support rest-schema shield waiting for review

Schema Inaccuracy

The assignees (issue and PR) and requested_reviewers and requested_teams (PRs) are required nullable arrays.

Experimentally it doesn't look like these are ever null in responses, nor is there any reason for them to be as an empty array should play that role just fine.

Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
3h 33m
Merged PRs (30d)
51

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.