Webfrontend #711

Centralize form option lists

Added by Alexander Blum over 5 years ago. Updated almost 5 years ago.

Status:NeuStart date:
Priority:NiedrigDue date:
Assignee:-% Done:


Category:-Estimated time:1.00 h
Target version:Repertoire 3) Testing phase III


Right now, there are multiple places for form options:

  • form controller, e.g. here
  • sequences, e.g. here
  • api, e.g. here

Sometimes there are multiple definitions of the same option list. It would be best, if we could just fetch the list from the tryton model itself (well, it's a tuple both in pyramid and tryton), but then we loose the possibility to translate the values.

I propose a central "views/forms/options.py", in which all options are declared and from where it should be imported by form controllers, api, etc.


#1 Updated by Alexander Blum over 5 years ago

  • Estimated time set to 1.00

#2 Updated by Alexander Blum almost 5 years ago

  • Target version changed from 3) Testing phase III to Repertoire 3) Testing phase III

#3 Updated by Alexander Blum almost 5 years ago

  • Project changed from repertoire to collecting_society

Also available in: Atom PDF