canmove, Confirmed users
1,570
edits
Extension Manager:API Rewrite: Difference between revisions
→Add-on states
(Created page with '=Overview= The current extension manager API is focussed on managing XPI style add-ons and is currently very limited forcing the UI and other callers to rely on direct access to ...') |
|||
| Line 8: | Line 8: | ||
=Add-on states= | =Add-on states= | ||
The new APIs represent add-ons in a number of states but these can broadly be split into two types | The new APIs represent add-ons in a number of states but these can broadly be split into two types, Local add-ons and Available add-ons. The API objects representing these add-ons are considered live views of the add-on. As operations are performed (disabling, downloading etc.) the properties of the object will update to reflect the new state. The objects represent add-on instances however. If I have an object representing the installed add-on "foo", then the user uninstalls and then reinstalls "foo" then the object still represents the old uninstalled instance of "foo". It is undefined whether retrieving the same add-on from the API twice will give two references to the same object or two separate objects that have the same properties. | ||
==Local add-ons== | ==Local add-ons== | ||