Skip to content
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

[Bug] [Meta] /UI/ can't handle a nested array parameter in the swagger spec #908

Closed
3 of 6 tasks
DaneelTrevize opened this issue May 10, 2018 · 2 comments
Closed
3 of 6 tasks
Labels
duplicate Issue is similar to an already existing one.

Comments

@DaneelTrevize
Copy link

DaneelTrevize commented May 10, 2018

Bug

https://esi.evetech.net/ui/#/Routes/get_route_origin_destination

While investigating #907, it was discovered that the UI doesn't seem to support producing nested arrays, let alone an array of pairs, for the connections parameter of the route endpoint.

Inputting destination: 30000142, origin: 30002187, and then attempting to build a connections pairing of: 30003522,30000144 will result in the UI adding a strange somewhat-associated pair of text fields and "Add Item" & "-" buttons, but any single or comma/space separated values cannot be successfully used and instead result in 400: Bad Request responses.

Response

Status Code

400

Body

For space-separated single field use:

{ "error": "failed to coerce value '[30003522' into type integer (format: int32), failed to coerce value '30000144]' into type integer (format: int32)" }

For comma-separated single field use:

{ "error": "too few items for '.connections'" }

Checklist

Check all boxes that apply to this issue:

  • Bug description is provided
  • Request path is provided
  • Response status code is provided
  • Response headers are provided
  • Response body is provided
  • Expected response is provided
@a-tal
Copy link
Contributor

a-tal commented May 10, 2018

esi/esi-swagger-ui#13

@a-tal a-tal closed this as completed May 10, 2018
@a-tal a-tal added the duplicate Issue is similar to an already existing one. label May 10, 2018
@DaneelTrevize
Copy link
Author

Any chance the endpoint description could be updated to link to that issue, so that devs see such a thing on /ui/ while it's not yet fixed? Or too nasty of a hack?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issue is similar to an already existing one.
Projects
None yet
Development

No branches or pull requests

2 participants