Ticket #4 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

Support child entities

Reported by: michael Assigned to:
Priority: medium Milestone: 0.3
Keywords: Cc:
Total Hours: 16.25 Billable?: 1
Add Hours to Ticket: 0 Dependencies:
Estimated Number of Hours: 0

Description

e.g. a URL template like /foo/{fooId}/bar/{barId}/{bazId} should map to parent /foo/{fooId}:FooFinder -> child /bar/{barId}:BarFinder -> child /{bazId}:BazFinder

Child entities need to be handled differently for Entity->URL generation since they don't know their parent's URL template. Initialisation would be by progression from parent to children. So if the URL passed to a parent contains remaining parts then the finder would act like a router to its children, otherwise behave as a normal finder.

Change History

11/02/08 13:53:33 changed by michael

  • hours set to 8.0.
  • totalhours changed from 0.0 to 8.0.

(In [3606]) Huge refactor to better support child entities and make cleaner customisation for complex entities. Refs #4, spent 8

11/02/08 15:05:32 changed by michael

  • hours set to 0.25.
  • totalhours changed from 8.0 to 8.25.

(In [3609]) Allow child resources to find their parents. Refs #4, spent 0.25

12/02/08 17:16:30 changed by michael

  • hours set to 8.0.
  • status changed from new to closed.
  • resolution set to fixed.
  • totalhours changed from 8.25 to 16.25.

(In [3613]) Working support for child entities. Supports full URL<->entity mapping. Fixes #4, spent 8