Closed
Bug 1190677
Opened 9 years ago
Closed 8 years ago
Need better type checking of arguments for open extension API
Categories
(WebExtensions :: Untriaged, defect, P2)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1208257
People
(Reporter: billm, Unassigned)
References
(Blocks 1 open bug)
Details
Right now arguments aren't checked at all. If the wrong type is passed in, weird things will probably happen. We should use the .json files that Google has for the API interfaces to check argument types. This would also simplify the handling of optional arguments.
|
Reporter | |
Comment 1•9 years ago
|
||
Link to how Google does this.
Flags: needinfo?(wmccloskey)
Priority: -- → P2
|
|
Reporter | |
Comment 2•9 years ago
|
||
Here's a sample JSON file: https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/extensions/api/windows.json&sq=package:chromium&type=cs&l=121
Flags: needinfo?(wmccloskey)
|
|
Reporter | |
Updated•9 years ago
|
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
|
||
Updated•9 years ago
|
|
||
Updated•9 years ago
|
Flags: blocking-webextensions+
|
|
||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
|
||
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•