enterprise-search

Following this spec: meilisearch/specifications#83

When indexing the _geo field as a filterable or sortable attribute, MeiliSearch should be able to parse string or numeric values rather than raise an invalid_geo_field error.

Please, feel free to ask any question to be helped by the core team if needed

The Results component should accept a prop called 'displayFields` which would allow users to specify which fields from their result object to display. The parameter should be able to express:

1. Order
2. field
3. field label

Example:

result:

{
  title: {title value},
  date: {date value},
  cats: {cats value }
  isbn: {isbn value}
}

Component using new field