Closed Bug 1576881 Opened 5 months ago Closed 4 months ago

Use custom type objects for complex props

Categories

(DevTools :: Application Panel, enhancement, P1)

enhancement

Tracking

(firefox71 fixed)

RESOLVED FIXED
Firefox 71
Tracking Status
firefox71 --- fixed

People

(Reporter: ladybenko, Assigned: ladybenko)

References

(Blocks 1 open bug)

Details

(Whiteboard: [manifest-reserve])

Attachments

(2 files)

We have places in our code where we specify props with PropType.array or PropType.object. We should actually specify how these arrays or objects look like. Since some of the types are being re-used, the proper way would be to use custom types, like we in remote debugging: https://searchfox.org/mozilla-central/search?q=&case=false&regexp=false&path=aboutdebugging%2F**%2Ftypes

Priority: -- → P3
Whiteboard: [triage]
Assignee: nobody → balbeza
Status: NEW → ASSIGNED
Priority: P3 → P1
Whiteboard: [manifest-reserve]
Pushed by balbeza@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/07c901d7f04e
Part 1: Use custom prop types for manifest components r=jdescottes
https://hg.mozilla.org/integration/autoland/rev/420cf92dd35c
Part 2: Use custom prop types for workers and routing components r=jdescottes
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71
You need to log in before you can comment on or make changes to this bug.