Ticket #9 (new discussion)

Opened 3 years ago

Last modified 21 months ago

Reorder fields in transactions using a convenience API

Reported by: mscott Owned by:
Priority: normal Milestone: Schevo 3.1
Component: All Components Keywords:
Cc:

Description (last modified by mscott) (diff)

There is currently no comfortable and consistent way to reorder fields in an object that maintains a FieldMap (i.e. transactions, views, entity instances, etc.)

API ideas:

  • .f.field_name.move_up(), .move_down(), .move_start(), .move_end()
  • Reorder the key list for an odict

Change History

Changed 3 years ago by mscott

  • description modified (diff)

Changed 3 years ago by mscott

pobrien: one idea is to simply add a single method to odict, like setorder() that took an iterable of keys that covered all the existing keys

pobrien: that way you just do keys = o.keys(); mangle(keys); o.setorder(keys)

pobrien: that frees up your mangling to be whatever you want

Changed 21 months ago by mscott

  • component set to All Components
  • milestone set to Schevo 3.1

Seems reasonable to get in by 3.1 final. pobrien, is this still an issue in some of the schemata you work with?

Note: See TracTickets for help on using tickets.