feat(API): improve get /projects/{project_id}/screenshots/{id} documentation#1168
feat(API): improve get /projects/{project_id}/screenshots/{id} documentation#1168Stephen Lumenta (sbl) wants to merge 3 commits into
Conversation
…ntation Addresses rubric dimensions: conceptual_clarity, error_documentation, example_quality, frontmatter_metadata, reference_completeness, schema_completeness, self_contained_examples, stable_identifiers, vocabulary_consistency. Adds a structured description with usage guidance, id-field semantics, branch and access-control notes, and an error-code table. Replaces placeholder path examples with realistic ids and adds expected-response comments. Fixes operationId from screenshot/show to screenshots/show. Enriches error response descriptions with specific causes and remediations. Part of DEVEX-115.
Adds inline 200 example, expands 403 error table with per-cause remediation, sharpens all error response descriptions, and updates conceptual description to reference feature requirement and branch behaviour explicitly. Dimensions addressed: conceptual_clarity, error_documentation, example_quality, reference_completeness, schema_completeness, self_contained_examples, stable_identifiers. Jira: DEVEX-115
…piled.json Renaming an operationId changes generated client method and model names in every SDK, which is a breaking change; the repo convention is singular resource names for single-resource operations (plural only for /list). The compare-output CI job requires the regenerated bundle to ship with the spec change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
|
||
| Use this endpoint when you have a screenshot's `id` (its string code) and need its current | ||
| metadata or image URL. To discover screenshot codes, first call the list endpoint | ||
| (`screenshots/list`); to inspect the individual markers attached to a screenshot, call the |
There was a problem hiding this comment.
it should be possible to hyperlink other endpoints
| (`screenshots/list`); to inspect the individual markers attached to a screenshot, call the | ||
| screenshot markers list endpoint. | ||
|
|
||
| **Feature requirement:** All screenshot endpoints require the Attachable Screenshots feature |
There was a problem hiding this comment.
internal implementation detail and shouldn't be exposed
| **Access control:** The access token must carry the `read` OAuth scope. The authenticated | ||
| user must have at least read permission on the project and on the screenshot resource. | ||
|
|
||
| **The `id` field is a string code, not a numeric primary key.** The value returned in the |
There was a problem hiding this comment.
no need to be described in the description, individual request fields are described in the parameters section below.
same goes for branch parameter below. if the parameter needs to be elaborated, that should be done in the corresponding parameter description in the parameters section below.
| codes for the project. | ||
| '429': | ||
| "$ref": "../../responses.yaml#/429" | ||
| description: >- |
There was a problem hiding this comment.
this description should be moved to 429 section in responses.yaml as it is identical for all requests.
|
Closing to re-run with updated fix-engine prompts (rules added for param-in-description and YAML section reordering). Fresh PRs incoming. |
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.
Jira: DEVEX-115