We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From #46
The text was updated successfully, but these errors were encountered: