ENGAGE-523: Implement a method for transforming models within the Nav List

Metadata

Source
ENGAGE-523
Type
Task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
Justin Obara
Created
2010-03-17T13:23:12.000-0400
Updated
2014-03-03T13:44:39.431-0500
Versions
N/A
Fixed Versions
  1. 0.3
Component
  1. NavigationList

Description

Implement a method for transforming models within the Nav List

Currently it seems that the model that the nav list should be acting on is rarely a one-to-one match to the nav list's actual model. In Engage we have been performing a mapping operation before passing it to the Nav List. It would simplify the use of the Nav List if it could transform the data itself.

Comments

  • Justin Obara commented 2010-03-17T13:23:23.000-0400

    Bug Parade Engage 0.3

  • Justin Obara commented 2010-03-23T16:32:37.000-0400

    Added the ability for the navlist to map data for its model on its own.

  • Justin Obara commented 2010-03-24T10:11:32.000-0400

    Assigned to Antranig for review

  • Antranig Basman commented 2010-03-25T08:42:26.000-0400

    I don't agree that this functionality should be part of the component - and certainly shouldn't be implemented by custom code delivered as part of the component file. In general, responsibility for mapping models really should fall upon the component's user and not on the component - but we should supply framework-standard functionality to help with this. In general we have developed a dangerous profusion of custom model-mapping schemes within Engage and I suggest that this implementation should probably be removed or migrated to a utility file pending a more thorough solution.