Closed Bug 641107 Opened 15 years ago Closed 15 years ago

warn users when libraries have conflicting module names

Categories

(addons.mozilla.org Graveyard :: Add-on Builder, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED
Builder 0.9.1

People

(Reporter: smcarthur, Assigned: smcarthur)

Details

Attachments

(1 file)

For now, while the SDK conflicts with modules of the same name regardless of the package, we should warn users about this issue. Make a Request getting all packages and modules associated with the currently editing package. Check for collisions for each case: 1) a new library is added 2) a library is updated to a new revision 3) a module is created 4) a module is renamed
Assignee: nobody → smcarthur
Priority: -- → P1
Target Milestone: --- → Builder 0.9.1
I can get the module lists and conflicted lists easily enough. What did we say should happen? Just a red roar? Should it reveal a separate roar for each conflicting module? Or should the roar contain all the modules that are conflicts?
One Roar listing the various conflicting modules. I almost have a work-up of the new messaging system, so we can get more advanced with UI next release ;)
OK, then i'll doing something like this from the attachment
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: