You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it returns an Error with a somewhat convex-specific string of BadUrl: Could not parse {url}`
To match the spec, we'd need our syscall to return a more complex json object and have the JS side convert/throw behavior that matches the public behavior.
Probably not super high pri - customers parsing error conditions does not seem super likely.
We shouldn't be changing these (they're often part of the spec for these JS builtins).
For some of these, we might be able to return something like { success: false, message: "..." } from the op and throw the error in JS
The text was updated successfully, but these errors were encountered:
Currently, it returns an Error with a somewhat convex-specific string of BadUrl: Could not parse {url}`
To match the spec, we'd need our syscall to return a more complex json object and have the JS side convert/throw behavior that matches the public behavior.
Probably not super high pri - customers parsing error conditions does not seem super likely.
We shouldn't be changing these (they're often part of the spec for these JS builtins).
For some of these, we might be able to return something like { success: false, message: "..." } from the op and throw the error in JS
The text was updated successfully, but these errors were encountered: