Skip to content

docs(asm): add response examples and fix missing operation descriptions#17

Merged
dmchaledev merged 2 commits into
mainfrom
claude/elegant-edison-td61c5
Jul 19, 2026
Merged

docs(asm): add response examples and fix missing operation descriptions#17
dmchaledev merged 2 commits into
mainfrom
claude/elegant-edison-td61c5

Conversation

@dmchaledev

Copy link
Copy Markdown
Contributor

Summary

  • Adds concrete JSON response examples to every success response across all 12 operations in asm/openapi.yaml. These appear as copy-pasteable example payloads in the ReDoc interactive docs, dramatically reducing time-to-first-integration for API consumers.
  • Fixes missing description fields on listTags and createTag (the only two operations without them), and adds a description to the status filter parameter in listScans, making the spec consistent throughout.

Why this matters

Before this change, the ReDoc docs showed schema structure but no concrete example values for any success response — developers had to make live API calls or reverse-engineer the schema to understand what real responses look like. After this change, every endpoint shows a realistic, copy-pasteable example JSON payload.

The examples use consistent fictional identifiers (acmecorp.com, ast_1a2b3c4d5e6f0001, etc.) and realistic data that demonstrates each field's purpose.

Test plan

  • Confirm Spectral lint passes (spectral lint asm/openapi.yaml --ruleset spectral:oas --fail-severity warn)
  • Verify ReDoc renders the new examples under each endpoint's "200 / 201 / 202" response tab
  • Check that all 12 operations now have descriptions

https://claude.ai/code/session_019sqEu3Tq6KRU4SzxQTia3f


Generated by Claude Code

claude added 2 commits July 19, 2026 14:30
Every success response now includes a concrete JSON example so developers
can see real-world payloads directly in the ReDoc interactive docs without
needing to make a live API call first. Also adds the missing `description`
fields to the `listTags` and `createTag` operations, and a `description`
to the `status` filter parameter on `listScans`.

https://claude.ai/code/session_019sqEu3Tq6KRU4SzxQTia3f
…mple check

Spectral (as pinned, spectral-cli 6.16.0) throws "Cannot read properties
of null (reading 'enum')" when an `example: null` sits under a schema
using OAS 3.1 array-form `type: [string, 'null']` (introduced by the
nullable-fix merge). The fields are optional/nullable, so omitting them
from the example is equally valid and avoids the crash.
@dmchaledev
dmchaledev force-pushed the claude/elegant-edison-td61c5 branch from dbf5d61 to 0a3bb4c Compare July 19, 2026 14:31
@dmchaledev
dmchaledev merged commit c8c3b9e into main Jul 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants