[Schema Inaccuracy] Example and schema mismatch for `#/paths/~1enterprises~1{enterprise}~1settings~1billing~1budgets~1{budget_id}/patch`

Open Beginner friendly
#5,588 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
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Start at the PATCH operation for #/paths/1enterprises1{enterprise}1settings1billing1budgets1{budget_id}/patch and inspect the #/components/examples/update-budget/value reference. Compare the example's budget_id field with the operation schema, then verify that the schema and example are synchronized.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

This is the json ref for the example

#/components/examples/update-budget/value

The field budget_id doesn't exist in the schema, but exists in the example.

Here's a snippet

    1: {
>   2:   "budget_id" : "2c1feb79-3947-4dc8-a16e-80cbd732cc0b",
                       ^
    3:   "message" : "Budget successfully updated."
    4: }

Expected

The schema and example are in sync

Reproduction Steps

I could reproduce this in

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