Skip to content

fix(API): improve post /projects/{project_id}/screenshots documentation#1182

Open
Stephen Lumenta (sbl) wants to merge 2 commits into
mainfrom
devex-115-screenshots-create-v2
Open

fix(API): improve post /projects/{project_id}/screenshots documentation#1182
Stephen Lumenta (sbl) wants to merge 2 commits into
mainfrom
devex-115-screenshots-create-v2

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.

Closes DEVEX-115

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

11 changes: 1 error, 0 warning, 10 info
error	[request-property-became-required] at doc/compiled.json
	in API POST /projects/{project_id}/screenshots
		the request property `filename` became required

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/api_name` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/default_encoding` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/default_file` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/description` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/exportable` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/extension` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/importable` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/includes_locale_information` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/name` became required for the status `200`

info	[response-property-became-required] at doc/compiled.json
	in API GET /formats
		the response property `items/renders_default_locale` became required for the status `200`

@sbl Stephen Lumenta (sbl) changed the title feat(API): improve post /projects/{project_id}/screenshots documentation fix(API): improve post /projects/{project_id}/screenshots documentation Jun 17, 2026
Comment thread paths/screenshots/create.yaml Outdated
Comment thread paths/screenshots/create.yaml Outdated
Stephen Lumenta (sbl) added a commit that referenced this pull request Jun 17, 2026
…ent_id}/keys

- Move the per-status prose out of the top-level description and onto the
  response objects (the pattern from #1182), removing the 'Errors:' block
  and the inline 'Returns 422 ...' sentence. (theSoenke)
- Normalize the branch parameter (query + body) to 'specify the branch to
  use', matching the wording used across the rest of the API rather than a
  bespoke 'When omitted, the main (default) branch is used.' (theSoenke)
- Fix the CLI v2 command: 'phrase figma_attachments create', not the
  non-existent 'phrase figma_attachment attach_to_key'. (theSoenke)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Drop the 'Requires the write scope and manage permission ...' sentence
  from the description; the 403 response already documents the write-scope
  and manage-permission requirement, and no other endpoint documents
  scopes in prose. (theSoenke)
- Normalize the branch property to 'specify the branch to use', dropping
  the unclear 'instead of the project default' wording, for consistency
  with the rest of the API. (theSoenke)

Co-Authored-By: Claude Opus 4.8 (1M context) <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.

2 participants