Closed
Bug 853177
Opened 12 years ago
Closed 12 years ago
promote Promise.js to toolkit
Categories
(Toolkit :: General, defect)
Toolkit
General
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Yoric, Unassigned)
References
Details
Given that the Promise module is starting to be used everywhere in the toolkit, is it still meaningful to get it from addon-sdk?
Comment 1•12 years ago
|
||
(In reply to David Rajchenbach Teller [:Yoric] <on workweek, will not follow bugzilla until March 26th> from comment #0)
> Given that the Promise module is starting to be used everywhere in the
> toolkit, is it still meaningful to get it from addon-sdk?
Sure, why not?
Reporter | ||
Comment 2•12 years ago
|
||
Architecturally, having core components (i.e. most of toolkit/) depend on extensibility components (addon-sdk/) is a little surprising. The fact that these extensibility components are based outside of mozilla-central makes things a little harder to manage.
However, the "real" solution might be on bug 810490 and the companion etherpad-based conversation.
Comment 3•12 years ago
|
||
(In reply to David Rajchenbach Teller [:Yoric] from comment #2)
> Architecturally, having core components (i.e. most of toolkit/) depend on
> extensibility components (addon-sdk/) is a little surprising.
"addon-sdk" may not be the best name given its intended purpose. I think it should generally be considered it a "core component". The ownership structures are different, of course, which seems to be the core issue here. If moving the code reduces friction to making required changes to it, I'm all for it.
Summary: Promise Promise.js to toolkit → promote Promise.js to toolkit
Reporter | ||
Comment 4•12 years ago
|
||
Mossop succeeded at convincing me that this probably won't be needed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•