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

consider swagger 3 upgrade #70

Open
codefromthecrypt opened this issue Apr 30, 2019 · 0 comments
Open

consider swagger 3 upgrade #70

codefromthecrypt opened this issue Apr 30, 2019 · 0 comments

Comments

@codefromthecrypt
Copy link
Member

codefromthecrypt commented Apr 30, 2019

From #46

The spans POST documentation is still a bit misleading. With the parameter named "spans", it seems to imply that it's expecting

{
    "spans": [{<...span...>}, {<....span...>}]
}

but it actually wants:

[{<...span...>}, {<...span...>}]

I couldn't figure out a way to acurately represent this in Swagger 2. It might be possible using Swagger 3 request body descriptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant