-
Notifications
You must be signed in to change notification settings - Fork 146
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
Import Firefox 66 beta3 schema. #2419
Conversation
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.
Thanks @EnTeQuAk, the update looks good and consistent with changes we applied on mozilla-central during the 66 cycle, there are only two details that worth a mention from my point of view:
- the change to the validation related to the incognito manifest property (on which I added some details in the comment below)
- this pretty weird test failure on the "should optionally scan selected files" test case while running on appveyor (which should be totally unrelated to the changes applied in this PR, and so not blocking on its own):
https://ci.appveyor.com/project/EnTeQuAk/addons-linter/builds/22024263/job/oinkf8kvga29na8f#L80
Do you mind to rerun the appveyor job? just to double-check that the failure is intermittent and not consistently reproduced.
@@ -104,7 +104,7 @@ | |||
"enum": [ | |||
"spanning" | |||
], | |||
"onError": "warn" | |||
"default": "spanning" |
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.
Just as a side note, this change means that extensions with "not_allowed" or "split" as the requested incognito mode will start to get errors when submitted on AMO.
The error message we currently report for this validation error is unfortunately not super useful, as it doesn't currently say which are the allowed values (currently just "spanning"):
Code Message Description File Line Column
JSON_INVALID "/incognito" should be equal to Your JSON file could not be parsed.
one of the allowed values
Shane checked with Mike how many of such extension we have, and they should be very few (I recall there were less then 10).
Anyway, Firefox will also raise an error an refuse to install the extension, and so the linter and AMO behavior is going to be consistent with Firefox.
That test is flaky, I have seen it failing before. Restarting should fix it. |
@wagnerand good, that's what I suspected, thanks for confirming it! |
I don't remember exactly, sorry. |
Fixes #2418