-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
toObject
with large long type is returning a wrong value
#690
Labels
Comments
@dcodeIO Please prioritize this, we have a customer escalation due to this. |
Please let me know if this solves your issue! |
@dcodeIO Yes could you also push a new minor release. Thanks again for the fast fix. |
@dcodeIO Thanks so much! This resolved the issue we were seeing. |
Now on npm! |
Repair very timely, very grateful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
protobuf.js version: 6.6.3
Calling
.toObject
with theNumber
option forlongs
is returning a value that's incorrect, at least for very largeLongs
(in our case, an epoch). Strangely, the result is different than callingtoNumber
on the specific field. Callingproto.toObject({ longs: Number })
is resulting in a different value thanproto.longValue.toNumber()
.The relevant shape of the object is:
The text was updated successfully, but these errors were encountered: