Skip to content

Conversation

@brizental
Copy link
Contributor

Now that we can acutally measure it, for reference:

  • The webext build is 46K.
  • The qt build is 44K.

@brizental
Copy link
Contributor Author

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)) {
Copy link
Contributor

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?

Copy link
Contributor Author

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.

brizental and others added 5 commits January 21, 2021 14:30
Co-authored-by: Alessio Placitelli <alessio.placitelli@gmail.com>
That is a browser API and fails at Qt/QML envs.
@brizental brizental force-pushed the 1687644-external-api branch from e81a250 to bea1bd6 Compare January 21, 2021 17:17
@brizental
Copy link
Contributor Author

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.

@brizental brizental requested a review from Dexterp37 January 21, 2021 17:19
@brizental brizental merged commit 09ae8b7 into mozilla:main Jan 22, 2021
@brizental brizental deleted the 1687644-external-api branch January 22, 2021 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants