The `custom field long choice` aim to provide a way to deal with choices
with a big possibilities.
The `custom field long choice` allow :
- to persist different options in the database ;
- each option has a key, a text (translatable string), and eventually a
parent, and an internal_key
- every key can be activate or not. If the parent is inactivated, all
childs are inactivated
- the internal key have two purposes :
- link to an external csv file, with their own key ;
- add a special class to results, to allow custom layout.
Currently, the field exists, but some elements are missing :
- a script for CSV import
- possibility to select multiple items
- edition of options
- handle of option without parents
- tests are missing
add a number field
The field has three option :
- lesser or equal than. If null, this option is ignored ;
- greather or equal than. If null, this options is ignored ;
- precision : the number of decimal after the number ;
- text after the field : a text to show after the field.
The field is rendered as an HTML integer input if precision = 0, or a
symfony number field if precision > 0.
ref chill-project/Chill-CustomFields#11
See merge request !6
The field has three option :
- lesser or equal than. If null, this option is ignored ;
- greather or equal than. If null, this options is ignored ;
- precision : the number of decimal after the number ;
- text after the field : a text to show after the field.
The field is rendered as an HTML integer input if precision = 0, or a
symfony number field if precision > 0.
ref chill-project/Chill-CustomFields#11
remove 'empty_data' which cause conflict with transformer
this blocked the possibility to uncheck the 'active' field on the
choice.
Should fix chill-project/Chill-CustomFields#12
See merge request !3
Layout of index page for customfieldsgroup
Fix chill-project/custom-fields#2 and chill-project/custom-fields#3
This is a test to see how works merge request in gitlab.
See merge request !1
The customFieldsGroup field is hidden when creating a new customFields.
The customFieldsGroup is retrieved from the url (`customFieldsGroup` value in the URL).
This should ease the task for administrator and be consistent with the UI which group customFields into customFieldsGroup.
