Closed benfoley closed 4 years ago
While adding types I also removed a setting value that was called "type". It was being used to do two things: first to set the type of UI element and also to hold info extracted from training files to build select options (eg with tier names etc). I removed this "type" value and added two separate parameters—ui_format and options. Now ui_format is used to determine the input component type, and options is used to hold file values and build the select options.
This makes ui settings for the
special-cases
andtranslation_tags
values that are used in cleaning the annotations.It required added a ui_format property to the import settings config stuff so that more control could be had over using types of input components. The type of input the ui used was determined by the type of ui setting set, but this was limited to str, int and list. I wanted the UI for
special-cases
andtranslation_tags
to be text area, and thought it best to have some mechanism for specifying that when defining the ui settings in elan transformer.Corresponding gui work is https://github.com/CoEDL/elpis-gui/pull/85