-
Notifications
You must be signed in to change notification settings - Fork 327
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
JSON Schema wrong for u128/i128 fields #1605
Comments
I think there is a difference between For more context, see
and in Why u128/i128 are serialized as strings in |
Thanks a lot for pointing this out. This is a big source of future problems.
Because whoever implemented it did not check |
This one is on me. I silently approved this by inaction due to holidays and other stuff in 2021. |
When using u128/i128 in messages, the generated schema wrongly outputs
"type": "integer"
instead of string.However, both json-serde and json-serde-wasm use strings for u128/i128. This is probably a bug to be fixed in schemars.
The text was updated successfully, but these errors were encountered: