Closed
Bug 1587126
Opened 5 years ago
Closed 5 years ago
Use of strongly typed enums (i.e. scoped enums) vs. non-scoped enums
Categories
(Core :: Storage: IndexedDB, task, P3)
Core
Storage: IndexedDB
Tracking
()
RESOLVED
FIXED
mozilla73
Tracking | Status | |
---|---|---|
firefox73 | --- | fixed |
People
(Reporter: sg, Assigned: sg)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Assignee | ||
Updated•5 years ago
|
Summary: Use pf strongly typed enums (i.e. scoped enums) vs. non-scoped enums → Use of strongly typed enums (i.e. scoped enums) vs. non-scoped enums
Updated•5 years ago
|
Priority: -- → P3
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → sgiesecke
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•5 years ago
|
||
Depends on D55117
Pushed by sgiesecke@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2f4851b50aeb
Declare that scoped enums should be used. r=dom-workers-and-storage-reviewers,janv,asuth
Comment 3•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox73:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in
before you can comment on or make changes to this bug.
Description
•