-
Notifications
You must be signed in to change notification settings - Fork 5.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
Error parsing javascript object to serde_json::Value #11502
Comments
@AaronO pointed out it's caused by rusty_v8's To summarize: needs a change in rusty_v8 before it can be fixed in deno. |
I've opened denoland/rusty_v8#740 to track the necessary changes to rusty_v8. |
Fixes: denoland#11502 Signed-off-by: Darshan Sen <[email protected]>
And finally, here's the PR that fixes the issue - #15946! :) |
Fixes: denoland#11502 Signed-off-by: Darshan Sen <[email protected]>
I'm using deno embedded in a rust application and we're facing an issue with the
serde_v8
with some objects.At some point in our script we call
await Deno.core.opAsync('success', message);
This
message
on the script side is an object, such as:On the rust side, my
success
function expects aserde_json::Value
object. This is failing to be serialised back to rust because it cannot handle the numbers as keys. Shouldn't deno convert them to string in this case?Even if I set the object like this:
deno still treats it as a number and fails to parse it.
The text was updated successfully, but these errors were encountered: