Skip to content

docs(API): improve get /projects/{project_id}/screenshots/{id} documentation#1189

Merged
Stephen Lumenta (sbl) merged 7 commits into
mainfrom
devex-115-screenshots-get-a-single-screenshot
Jul 1, 2026
Merged

docs(API): improve get /projects/{project_id}/screenshots/{id} documentation#1189
Stephen Lumenta (sbl) merged 7 commits into
mainfrom
devex-115-screenshots-get-a-single-screenshot

Conversation

@sbl

Copy link
Copy Markdown
Contributor

Improves the documentation for get /projects/{project_id}/screenshots/{id}: sharper descriptions, parameter docs, error responses, and usage examples.

Drafted with AI assistance and grounded in the API implementation. Please review for technical accuracy before merging; nothing is merged automatically.

🤖 Generated with Claude Code

@sbl Stephen Lumenta (sbl) added the developer-hub-api-quality API doc quality fix from the API Grader label Jun 15, 2026
@github-actions

github-actions Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

API changelog (oasdiff)

Doc-only edits (descriptions, examples) do not appear here.

3 changes: 0 error, 0 warning, 3 info
info	[new-optional-request-property] at doc/compiled.json
	in API DELETE /projects/{project_id}/keys/{id}/key_links
		added the new optional request property `strategy`

info	[request-body-became-optional] at doc/compiled.json
	in API DELETE /projects/{project_id}/keys/{id}/key_links
		request body became optional

info	[response-media-type-added] at doc/compiled.json
	in API DELETE /projects/{project_id}/keys/{id}/key_links
		added the media type `application/json` for the response with the status `200`

@sbl

Copy link
Copy Markdown
Contributor Author

This PR replaces #1168, which was closed after jablan's review.

Feedback addressed from #1168:

Comment Status
"Internal implementation detail and shouldn't be exposed" ✅ Fixed
"No need to describe id/branch in the description — that belongs in parameters" ✅ Fixed
"429 description is identical for all requests — move to responses.yaml" ✅ Fixed
"It should be possible to hyperlink other endpoints" ⚠️ Not addressed — see note below

What changed:

  • branch elaboration is moved to the parameter's own description field in parameters:. The top-level description no longer restates individual request fields.
  • Internal detail removed from the description body.
  • 429 now uses a bare $ref: "../../responses.yaml#/429" with no inline description override.

Open item — hyperlinks: Related endpoints are referenced in plain prose rather than as Markdown links. If clickable cross-references are a hard requirement, let us know and we'll update the description accordingly.

🤖 Generated with Claude Code

@sbl Stephen Lumenta (sbl) changed the title feat(API): improve get /projects/{project_id}/screenshots/{id} documentation fix(API): improve get /projects/{project_id}/screenshots/{id} documentation Jun 17, 2026
Apply the batch review conventions:
- Move the 'Error reference' table out of the top-level description and
  onto the response objects (400/401/403/404/429 carry their own
  description); keep only purpose and the feature-availability note.
- Normalize the branch parameter to 'specify the branch to use'.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sbl Stephen Lumenta (sbl) changed the title fix(API): improve get /projects/{project_id}/screenshots/{id} documentation docs(API): improve get /projects/{project_id}/screenshots/{id} documentation Jun 17, 2026
Stephen Lumenta (sbl) and others added 5 commits June 24, 2026 09:07
Review feedback: error response descriptions should stay in the shared
responses.yaml for consistency, not be re-authored inline per operation.
Under OpenAPI 3.0 a description sibling of $ref is ignored anyway, so the
inline text never rendered. Strip the inline $ref-sibling response
descriptions (now bare $refs); the shared response owns the wording.
Genuinely custom (non-$ref) response bodies are left intact.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Strings convention: never hand-author Curl or CLI v2 samples. Mintlify
renders the request sample (curl + the multi-language playground) and the
response from the OpenAPI operation itself, so a hand-written x-code-samples
block drifts and overrides the correct auto-generated one; a CLI v2 sample
is not spec-derivable at all. Remove the block so Mintlify renders.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
New strings rubric rule: Mintlify auto-generates the request curl, so a
hand-written Curl sample is redundant and overrides it, but a CLI v2
sample cannot be derived from the spec and must be preserved. This PR
originally removed the whole x-code-samples block; restore the CLI v2
entry (Curl stays dropped). compiled.json regenerated via make bundle.
example: my-feature-branch
name: branch
in: query
required: false

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

branch parameter should be available in parameters.yaml to be used as a reference. we should double check if all current usages are non-required (most should be), and then add this flag there as well. perhaps as a separate PR

@sbl Stephen Lumenta (sbl) merged commit c02b3dc into main Jul 1, 2026
13 checks passed
@sbl Stephen Lumenta (sbl) deleted the devex-115-screenshots-get-a-single-screenshot branch July 1, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

developer-hub-api-quality API doc quality fix from the API Grader

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants