Closed
Bug 1217358
Opened 10 years ago
Closed 10 years ago
Parse Web Extensions' manifest.json on submission
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: magopian, Assigned: magopian)
References
Details
Attachments
(3 files)
When submitting the add-on to AMO: we need a new "Extractor" subclass (https://github.com/mozilla/olympia/blob/a926e1d7f2323c778e638bf82483ae45372608f3/apps/files/utils.py#L86) to deal with the manifest.json format.
| Assignee | ||
Comment 1•10 years ago
|
||
Assignee: nobody → magopian
Iteration: --- → 44.2 - Oct 19
Updated•10 years ago
|
Iteration: 44.2 - Oct 19 → 44.3 - Nov 2
Comment 2•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/olympia
https://github.com/mozilla/olympia/commit/2a91832145fd21e90a703dbf65015181b29f359c
Parse the WebExtension's manifest on submission (bug 1217358)
https://github.com/mozilla/olympia/commit/6bba63313faf0ace65073a2995f36a032a7e0ffe
Merge pull request #839 from magopian/1217358-parse-webextension-manifest-on-submission
Parse the WebExtension's manifest on submission (bug 1217358)
| Assignee | ||
Comment 3•10 years ago
|
||
The current work only allows the submission on AMO, but it's still rejected/unrecognized by the validator (this is bug 1217810).
See the attachment for an idea of what it should look like. I've also attached an example Webextension to this bug for testing.
For a comparison, see the other screenshot for how it looked before AMO would accept the submission of webextensions.
| Assignee | ||
Comment 4•10 years ago
|
||
| Assignee | ||
Comment 5•10 years ago
|
||
Find some more example WebExtensions on https://github.com/mdn/webextensions-examples
Updated•10 years ago
|
Iteration: 44.3 - Nov 2 → 45.1 - Nov 16
| Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•