Skip to content

feat(API): improve post /projects/{project_id}/screenshots documentation#1171

Open
Stephen Lumenta (sbl) wants to merge 3 commits into
mainfrom
devex-115-screenshots-create-a-screenshot
Open

feat(API): improve post /projects/{project_id}/screenshots documentation#1171
Stephen Lumenta (sbl) wants to merge 3 commits into
mainfrom
devex-115-screenshots-create-a-screenshot

Conversation

@sbl

Copy link
Copy Markdown
Contributor

Improves the documentation for post /projects/{project_id}/screenshots: 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.

Addresses rubric dimensions: conceptual_clarity, error_documentation,
example_quality, frontmatter_metadata, reference_completeness,
schema_completeness, self_contained_examples, stable_identifiers.

- Expands description with workflow context, file upload requirements,
  side effects, access control matrix, and branch guidance
- Fixes operationId to screenshots/create (was screenshot/create)
- Adds required: [filename] constraint to request body schema
- Adds realistic inline example on 201 response
- Expands 403 description to enumerate all distinct forbidden cases
- Improves all property descriptions with actionable language
- Replaces placeholder :project_id curl URL with a concrete example ID
- Removes non-standard filename binary example value

Part of DEVEX-115
…ields for POST screenshots

Adds per-status-code descriptions for 400, 401, 404, 422, 429; adds `name`
to the required fields list; enriches the description field with accepted
formats, name uniqueness, and file upload constraints.

Addresses DEVEX-115 dimensions: error_documentation, schema_completeness,
reference_completeness, example_quality, self_contained_examples.
@sbl Stephen Lumenta (sbl) added the developer-hub-api-quality API doc quality fix from the API Grader label Jun 10, 2026
…elds, regenerate bundle

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

name drops out of the required list: the model derives a name from the
uploaded file's name on create (before_validation
:derive_name_from_filename), so only filename is genuinely required.
The name property description documents the derivation.

The compare-output CI job requires the regenerated doc/compiled.json
bundle to ship with the spec change.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant