[Schema Inaccuracy] Example and schema mismatch at patch-schema

Open Beginner friendly

#4,470 opened on Jan 26, 2025 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 65/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Stale
Tech stack: json, openapi
Domain: api

Research direction

Open descriptions-next/ghes-3.13/ghes-3.13.json and inspect the schema and example locations given in the report. Compare the patch operation value definition with the addMembers example, update either side so they agree, and verify that the example parses against the schema.

Written by the indexing model from the issue text.

Description

documentation

Schema Inaccuracy

The schema at this location is

#/components/schemas/patch-schema/properties/Operations/items/properties/value

                "value": {
                  "type": "string",
                  "description": "Corresponding 'value' of that field specified by 'path'"
                }

The example at is

#/paths/~1scim~1v2~1enterprises~1{enterprise}~1Groups~1{scim_group_id}/patch/requestBody/content/application~1json/examples/addMembers/value

          {
            "Operations" : [ {
              "op" : "add",
              "path" : "members",
              "value" : [ {
                "value" : "879db59-3bdf-4490-ad68-ab880a2694745"
              }, {
                "value" : "0db508eb-91e2-46e4-809c-30dcbda0c685"
              } ]
            } ],
            "schemas" : [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ]
          }

The value cannot be parsed.

Expected

Either the example or schema is updated to match the other.

Reproduction Steps

This has been observed on

https://github.com/github/rest-api-description/raw/main/descriptions-next/ghes-3.13/ghes-3.13.json

I've checked for this in 3.10, 3.11, 3.12, 3.13, 3.14.

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

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

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026
🧹 Extract DRA resource collection and charge calculation helpers Open

kind/cleanup

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

kubernetes-sigs/kueue#15937 · Opened Sep 21, 2026
Custom provider credential is written as `PROVIDER_API_KEY` (apiserver) but the AgentRun controller injects only allowlisted keys, so every custom provider fails with HTTP 401 Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

sympozium-ai/sympozium#627 · Opened Sep 21, 2026

More Backend & API Design issues