feat(spec): parlay command endpoints (toilville-design#177) #18
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/spec-parlay-commands"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Describes the parlay command endpoints served by ritual-engine#891, over spel#1080's contract:
GET /api/v1/parlays/{parlay_id}/commandsPOST /api/v1/parlays/{parlay_id}/commandsParlayCommandRequest,ParlayCommandResult,AvailableParlayCommand,ParlayCommandList.GET /api/v1/events.openapi.yamlgoes to 0.64.0.Merge after ritual-engine#891 and spel#1080, since this repo describes only endpoints the server serves.
Testing
openapi-spec-validatorpasses onopenapi.yaml.tools/check_schema_registry.pypasses (6 files).pytestpasses: 18 passed, 1 xfailed (unchanged).parlay_commandtests parse.Impact Statement
listParlayCommandsandapplyParlayCommand, under the existinggovernancetag.GET /api/v1/events's visibility text now includes frame parlays for the steward.parlay_idis the frame parlay'sframe_id.Docs
CHANGELOG Unreleased has a "parlay commands" section covering what is added and changed, and what is left out (the dormant voting kernel and a command topic).
Describes ritual-engine#891 over spel#1080: GET/POST /api/v1/parlays/{parlay_id}/commands with ParlayCommandRequest, ParlayCommandResult, AvailableParlayCommand and ParlayCommandList, and the events stream's new steward rule for frame-parlay facts. 0.64.0.