[Schema Inaccuracy] Example and schema mismatch for `#/paths/~1orgs~1{org}~1projectsV2/get`

Open
#5,599 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the #/paths/1orgs1{org}~1projectsV2/get endpoint and compare its response schema with #/components/examples/projects-v2/value. Verify whether the response is an array or a single element, then update the schema or example so their shapes match and confirm the endpoint description remains consistent.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

This is the json ref for the example

#/components/examples/projects-v2/value

Schema and example mismatch. The schema suggests the response is an array. The example has an element.

Here's a snippet

>   1: {
    2:   "closed_at" : null,
    3:   "created_at" : "2011-04-10T20:09:31Z",
    4:   "creator" : {
    5:     "login" : "octocat",

Expected

The schema and example are in sync

Reproduction Steps

I could reproduce this in

  • fpt
  • ghec
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.