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

When returning longs, the least significant 8 bits seem to be changed. #392

Closed
j7nw4r opened this issue May 4, 2017 · 4 comments
Closed

Comments

@j7nw4r
Copy link

j7nw4r commented May 4, 2017

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

@j7nw4r 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 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
@bryjshed
Copy link

Any news or fix about this? We are also facing this issue.

@domaindrivendev
Copy link
Owner

This sounds like a swagger-ui issue - you'll have better luck posting to that repo

@j7nw4r
Copy link
Author

j7nw4r commented Jun 1, 2017

Thank you @domaindrivendev

For those that care: swagger-api/swagger-ui#3141

@domaindrivendev
Copy link
Owner

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants