-
Notifications
You must be signed in to change notification settings - Fork 34
Bug 1687644 - Implement the external API for consumers #27
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
Conversation
|
The Qt error seems unrelated. I will verify, but don't feel that it blocks the review :) |
| if (isObject(target) && key in target) { | ||
| target = target[key]; | ||
| const temp: unknown = target[key]; | ||
| if (isJSONValue(temp)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you stumble upon non-JSON values being stored?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, but we can and typescript compilation errors because it knows we can. It requires that we guarantee that the type is correct.
Co-authored-by: Alessio Placitelli <alessio.placitelli@gmail.com>
That is a browser API and fails at Qt/QML envs.
e81a250 to
bea1bd6
Compare
|
The Qt problems were actually related. We were using some browser APIs namely URL and crypto, which I didn't realize before. That was fixed. This is ready for a new look. |
Now that we can acutally measure it, for reference: