Closed
Bug 903268
Opened 11 years ago
Closed 9 years ago
Not using a default value in preferences needs documentation
Categories
(Add-on SDK Graveyard :: Documentation, defect, P3)
Add-on SDK Graveyard
Documentation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: evold, Assigned: evold)
Details
(Whiteboard: [good first bug])
Attachments
(1 file)
From IRC "Mook notes that preferences doesn't document what happens if you don't supply a default value..."
Assignee | ||
Updated•11 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Updated•11 years ago
|
Whiteboard: [good first bug]
Priority: -- → P3
Updated•10 years ago
|
Summary: Document what happens when one does not use a default value → Not using a default value in preferences needs documentation
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8566696 -
Flags: review?(jsantell)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → evold
Updated•9 years ago
|
Attachment #8566696 -
Flags: review?(jsantell) → review+
Comment 2•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/791ea4f0e0459c37275595503a7849c3872619ec Bug 903268 add a test for the case of getting a pref that dne and where we use no default value https://github.com/mozilla/addon-sdk/commit/ec54a8b2c2fb043684e5c9ba9c64e269bd56b349 Merge pull request #1866 from erikvold/903268 Bug 903268 Add a test for the case of getting a pref that DNE and where we use no default value r=jsantell
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•