[Schema Inaccuracy] Example and schema mismatch for `#/paths/~1orgs~1{org}~1insights~1api~1subject-stats/get`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- openapi
- Domain
- api
Research direction
Start with the OpenAPI definition for GET /orgs/{org}/insights/api/subject-stats and the referenced example at #/components/examples/api-insights-subject-stats/value. Compare the schema with the shown example in both FPT and GHEC, then update the definition so integration_id is represented consistently. Done means the schema and example are in sync.
Written by the indexing model from the issue text.
Description
Schema Inaccuracy
This is the json ref for the example
#/components/examples/api-insights-subject-stats/value
The field integration_id doesn't exist in the schema, but exists in the example.
Here's a snippet
1: [ {
2: "subject_type" : "installation",
3: "subject_id" : 954453,
4: "subject_name" : "GitHub Actions",
> 5: "integration_id" : 124345,
6: "total_request_count" : 544665,
7: "rate_limited_request_count" : 13,
8: "last_request_timestamp" : "2024-09-18T15:43:03Z",
9: "last_rate_limited_timestamp" : "2024-09-18T06:30:09Z"
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
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.
More from github/rest-api-description
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/rest-api-description#7201 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/rest-api-description#7163 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7162 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7135 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/rest-api-description#7111 · 1 comment ·
All issues in github/rest-api-description
Similar issues
-
area/sessions comp/cron comp/gateway P2 sweeper:risk-message-delivery sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#118863 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·