Open cjrutherford opened 3 months ago
I like the OpenAPI spec, Ideally we should have some automatic way of checking it's in sync with the real API. This seem not quickly doable but IIRC you can build "tester web site " out of the spec, can we expose/have instruction to build it locally so that at least one can manual test it?
There is some naming confusion I would fix, like btcd
instead of bitcoin
in the file name (btcd
recall a different software, the node written in go) and also a typo in the commit message (lnd
instead of liquid
)
I like the OpenAPI spec, Ideally we should have some automatic way of checking it's in sync with the real API. This seem not quickly doable but IIRC you can build "tester web site " out of the spec, can we expose/have instruction to build it locally so that at least one can manual test it?
There is some naming confusion I would fix, like
btcd
instead ofbitcoin
in the file name (btcd
recall a different software, the node written in go) and also a typo in the commit message (lnd
instead ofliquid
)I like the OpenAPI spec, Ideally we should have some automatic way of checking it's in sync with the real API. This seem not quickly doable but IIRC you can build "tester web site " out of the spec, can we expose/have instruction to build it locally so that at least one can manual test it?
There is some naming confusion I would fix, like
btcd
instead ofbitcoin
in the file name (btcd
recall a different software, the node written in go) and also a typo in the commit message (lnd
instead ofliquid
)
we can do a validation with a generated client (e.g. https://openapi-generator.tech/)
I like the OpenAPI spec, Ideally we should have some automatic way of checking it's in sync with the real API. This seem not quickly doable but IIRC you can build "tester web site " out of the spec, can we expose/have instruction to build it locally so that at least one can manual test it? There is some naming confusion I would fix, like
btcd
instead ofbitcoin
in the file name (btcd
recall a different software, the node written in go) and also a typo in the commit message (lnd
instead ofliquid
)I like the OpenAPI spec, Ideally we should have some automatic way of checking it's in sync with the real API. This seem not quickly doable but IIRC you can build "tester web site " out of the spec, can we expose/have instruction to build it locally so that at least one can manual test it? There is some naming confusion I would fix, like
btcd
instead ofbitcoin
in the file name (btcd
recall a different software, the node written in go) and also a typo in the commit message (lnd
instead ofliquid
)we can do a validation with a generated client (e.g. https://openapi-generator.tech/)
should I create a generated client and set it up to auto test?
Fully validated requests with the exception of the broadcast and tx routes to post a transaction to the chain.
everything else has been documented with the correct shape of the response.
work on request body is dependent on testing of the broadcast and tx routes as mentioned above.
all other routes tested properly.