Fix searching number fields

[hwbllmnn]

FEATURE

Description:

This PR fixes searching number fields via WFS. This is still far from perfect. You can configure the WFS search now with attribute details, which allows you to control how filters are created. matchCase can be used to control the corresponding filter attribute, exactSearch will make the code check for attributes of type number and int and skip the filter completely if the search term contains non numeric characters.

We should really think about doing a solr or elastic search backend in order to get better results.

@terrestris/devs Please review.

[KaiVolland]

Very nice.
Just one minor change-request to be more clear about the attributeDetails.

[KaiVolland]

Please make use of PropTypes.shape.
This way you can define the existing detail keys and their types.
e.g.:

// An object taking on a particular shape
  attributeDetails: PropTypes.shape({
    exactSearch: PropTypes.bool,
    type: PropTypes.oneOf(['int', 'string', 'number', …]),
    …
  })

[hwbllmnn]

Alright, added in 3dec246.

[KaiVolland]

Nice. Didn't expect teh attribtueDetails as this complex but it looks quite strict now. 👍

So i guess the structure is something like this?:

{
  layer1: [{
    attribute1: {
      matchCase: true,
      type: 'number',
      exactSearch: false
    },
    attribute2: {
      matchCase: false,
      type: 'string',
      exactSearch: true
    },
    …
  }],
  layer2: […],
  …
}

[hwbllmnn]

Yes, exactly. It looks quite complex, but at least it matches the structure of the searchAttributes prop and makes accessing it easy. In an ideal world we should merge those two into a new structure, I just wanted to keep backwards compatibility.