-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs in swagger #199
Comments
Hey @lil131 (2) is definitely a bug: Did you fancy submitting a PR to fix that? However, (1) is actually accurate I believe - it's generated from this code, which is the source of truth: However, there are some old docs that are referring to an API that was renamed (and you should find the old API still exists in the swagger, but is marked deprecated): Wonder if you fancied updating that doc as well in your PR? |
Note - in addition to The fact that these have been incorrect for a while also implies they're not tested E2E (so the fix should probably include an E2E test as well). |
btw the Swagger schemas for these particular routes are written out by hand, rather than being generated from the Go code. That explains how they got out of sync (and it's somewhat of a concern to me in general) - but assuming we aren't changing that immediately, the schemas can be found in |
Thanks @peterbroadhurst and @awrichar! Just sent a PR for this, also included |
should be
/namespaces/{ns}/broadcast/message
https://github.com/hyperledger-labs/firefly/blob/d20e6faa73061d176165c926ce32696025d79d33/docs/swagger/swagger.yaml#L2560
should be
topics
with typestring[]
https://github.com/hyperledger-labs/firefly/blob/d20e6faa73061d176165c926ce32696025d79d33/docs/swagger/swagger.yaml#L2617
The text was updated successfully, but these errors were encountered: