-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
When returning longs, the least significant 8 bits seem to be changed. #392
Comments
j7nw4r
changed the title
When returning longs, the lease significant 8 bits seem to be changed.
When returning longs, the leaset significant 8 bits seem to be changed.
May 5, 2017
j7nw4r
changed the title
When returning longs, the leaset significant 8 bits seem to be changed.
When returning longs, the least significant 8 bits seem to be changed.
May 5, 2017
Any news or fix about this? We are also facing this issue. |
This sounds like a swagger-ui issue - you'll have better luck posting to that repo |
Thank you @domaindrivendev For those that care: swagger-api/swagger-ui#3141 |
Sounds like this is a JavaScript limitiation - so going to close as there really isn't much that can be done on the Swashbuckle side. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When returning longs to the Swashbuckle UI, it seems that the long's aren't returned correct. When using Postman, the returned longs are correct. There doesn't seem to be the same issue when returning any other numeric type.
Example repo: https://github.com/johnathan-walker/SwaggerUILongBug
The text was updated successfully, but these errors were encountered: