Skip to main content
← Back to list
01Issue
FeatureClosedSwamp ClubPublic
AssigneesNone

Relationships

#3176 Docs: extension info reference should show the Accepted warnings block and contentMetadata.acceptances (swamp-club#3158)

Opened by skunk-ape · 10/8/2026

What changed

swamp-club#3158 shipped in swamp v20261008.143625.0-sha.ee36b409 (swamp PR #2925). swamp extension info now shows the declared acceptances that the registry returns for the latest version (swamp-club#3095).

  • Log mode: an Accepted warnings block is printed after the content listing and before Downloads. It uses the same line format as push's Accepted warnings block:
    • the generated declaration line, when the extension has one;
    • one line per entry: rule, an em dash, then file:line, or (extension) when the entry has no file;
    • : reason after the location, when the author gave one;
    • and N more when total exceeds the entries the registry returned (it keeps the first 500).
  • Paths and escaping: files are archive paths (models/...), and control characters in text the author wrote are escaped.
  • JSON mode: contentMetadata.acceptances is { accepted: [{ rule, file?, line?, reason?, source }], generated?: { by, source, commit }, total }. The registry's nulls are left out. The key is absent when the version declared none, or when the registry predates #3095.

Page to update

content/manual/reference/extensions/management.md, section ## info:

  • Output: add the Accepted warnings block to the sample output, or show it in a second example, and add a sentence saying what it lists and that it appears only when the latest version declared acceptances.
  • JSON shape: add acceptances under contentMetadata, with the field table, the omitted-nulls note and the absent-when-none note.

Suggested sample (real output from a local registry)

extension·info: Accepted warnings:
extension·info:   generated by swamp-extensions/codegen from https://api.example.com/openapi.yaml at 0123abcd
extension·info:   ipv4-address-literals — models/hosts.txt:2: documented lab addresses
extension·info:   testing-completeness — models/ext/accepted.ts
extension·info:   credentials-sensitive-field — models/ext/accepted.ts:13: a placeholder the docs example fills in
extension·info:   credentials-sensitive-field — models/ext/accepted.ts:14

The Registry subsection of content/manual/reference/extensions/publishing.md already documents the server-side field (#3095). It could link to extension info as the way to see acceptances from the CLI.

02Bog Flow
✓OPEN○TRIAGED○IN PROGRESS◉CLOSED

Closed

10/8/2026, 6:34:05 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

stack72 commented 10/8/2026, 6:34:05 PM

Documented in swamp-club PR #1314 (merged). content/manual/reference/extensions/management.md, section info: the Accepted warnings block (declaration line, rule — file:line or (extension), : reason, and N more), archive paths and control-character escaping, and that it appears only when the latest version declared acceptances. The JSON shape documents contentMetadata.acceptances with a field table, omitted nulls, and the key being absent when none were declared or the registry predates #3095. The Registry subsection of publishing.md now links to extension info.

Sign in to post a ripple.