Override filtration

[Dergash]

There are cases when filtration for the field should work in a non-standard way: for example, a picklist field sometimes needs to be searched by substring instead of selecting values from the list.

Proposed solution is to have two fields: one for display purposes and another for filtration purposes. The second field is supposed to be hidden, but its key and type are used to decide on filtration control and logic for displayed purposes.

Proposed schema extension:

export interface WidgetFieldBase {

  // ...

  /**
    * When assigned with another field key, this another will be used for filtration purposes 
   */
  filterBy?: string
}

Configuration example:

// example.widget.json
{

    // ...

    "fields": [
      {
        "title": "Address",
        "key": "address",
        "type": "input",
        "filterBy": "addressFilter"
      },
      {
        "title": "Address Specified",
        "key": "addressFilter",
        "hidden": true,
        "type": "checkbox"
      }
    ]
  }