chore: update openapi.yml for solver-driver communication #2182
Assignees
Labels
E:3.1 Driver Colocation
See https://github.com/cowprotocol/pm/issues/14 for details
Comments
|
I'll look into updating the yaml files |
fleupold
added
the
E:3.1 Driver Colocation
This was referenced Dec 19, 2023
Merged
fleupold
added a commit
that referenced
this issue
Dec 21, 2023
# Description The driver API is not up to date. # Changes - [x] Add reveal endpoint - [x] Update all existing fields - [x] Add feePolicy fields - [x] Flatten and tag feePolicy enum in-line with remaining enums (e.g. Liquidity) ## How to test Pasted the text in to see it render correctly ## Related Issues Part of #2182
fleupold
added a commit
that referenced
this issue
Dec 21, 2023
# Description Docs were slightly out of date # Changes - [x] Updates all fields and structs on the existing endpoint - [x] Remove pre-interactions for jit orders (for some reason we didn't populate post interactions and since those orders aren't really used in practice anyways, it seemed simpler to remove pre interactions instead of adding post interactions). - [x] Flatten notification type to make it consistent with the way we encode enums elsewhere in the new API (cf. `Liquidity`) - [x] Flatten Score enum to make it consistent - [x] Document notify endpoint ## How to test Past into https://editor.swagger.io/ and compare line by line with the rust structs ## Related Issues Fixes #2182
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Solvers are supposed to change their solver engines to receive auctions and return solutions conforming to a new API.
However, the specification in
openapi.ymlseems to be out of sync with what is actually used in the communication between driver and solver here and here.Acceptance criteria
openapi.ymlto be consistent with the rust codeThe text was updated successfully, but these errors were encountered: