Closed Bug 1067134 Opened 11 years ago Closed 2 years ago

DRY up the calendar properties and components code

Categories

(Calendar :: Internal Components, defect, P3)

Product:
Calendar
Component:
Internal Components
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Fallen, Unassigned)

References

(Blocks 1 open bug)

Details

No description provided.
Our code for relations,attendees,attachments is very similar, we should DRY it up. I have some work in progress code for this.
Blocks: 702206
Summary: DRY → DRY up the calendar properties and components code
Priority: -- → P1
Priority: P1 → P2

Not clear to me what this was about?

Priority: P2 → P3

Those three object types are sugar on top of the basic components, there are a lot of repeating methods like get/setProperty, ical generation and properties, immutibility code. I think we could shorten a lot of this into a common class. I can check what the patch I mentioned looks like.

Assignee: philipp → nobody
Status: ASSIGNED → NEW
OS: All → Unspecified
Hardware: All → Unspecified
Version: Trunk → unspecified
Severity: normal → S3

Unlikely my code from 4 years ago is meaningfully useful here. I still think our component code is too complicated, but probably better for someone to just take a fresh stab at it.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.