See #153
This removes it and allows the actual field/type of field searched for to deal with "contains". There is no "starts" with in Solr/Lucene but an exact match will happen if the field is a non-full-text string.
Also note for @alliomeria we have been doing this a bit wrong! The actual searched fields are part of the Options on the top, the filter we add is basically "useless". It always uses the configured "fields", the "filters" are used as additional to the the autocomplete match. I hate Drupal sometimes!
See #153 This removes it and allows the actual field/type of field searched for to deal with "contains". There is no "starts" with in Solr/Lucene but an exact match will happen if the field is a non-full-text string.
Also note for @alliomeria we have been doing this a bit wrong! The actual searched fields are part of the Options on the top, the filter we add is basically "useless". It always uses the configured "fields", the "filters" are used as additional to the the autocomplete match. I hate Drupal sometimes!