Feature: Add support for `nested` object mapping

[siddharthlatest]

Issue Type:

Enhancement

Platform:

ReactiveSearch for Web

Description:

ReactiveSearch today doesn't support querying the fields of an object field with a nested mapping.

A nested object requires a different query (where a path for the nested field needs to be specified) along with the original query. The same applies to an aggregation.

This issue proposes to add a nestedField prop in all the data-driven components we have to support the use-case of a nested object.

Prop definition for the field looks like:

nestedField String [optional]
When your dataField is present inside an object of type nested, this can be used to set the path of the nested field. Setting this allows searching within documents belonging to the path.

Reactivesearch version: x.y.z

2.12.1

Components to support this in:

• MultiDropdownList
• SingleDropdownList
• MultiList
• SingleList
• SingleRange
• MultiRange
• SingleDropdownRange
• MultiDropdownRange
• DataSearch
• CategorySearch
• TextField
• ToggleButton
• TagCloud
• SingleDataList
• MultiDataList
• RangeSlider
• DynamicRangeSlider
• RangeInput
• NumberBox
• DatePicker
• DateRange
• RatingsFilter
• GeoDistanceSlider
• GeoDistanceDropdown

[aol-nnov]

@metagrover here is my contrib for nested fields in MultiList. Should I make a PR?

aol-nnov@a797ba6

[metagrover]

@aol-nnov Left the reviews on the commit. Thanks for taking out the time to work on this!

[aol-nnov]

Thanks, I'll revisit the changes soon.

It worked for me months before, but I was never confident if it's a clear fix for nested fields.

[aol-nnov]

@metagrover I've redone my changes in MultiList.

My previous idea was to store "nested" part of property name in nestedField
i.e. vendor is nested object with field name

dataField: 'name'
nestedField: 'vendor'

(it was some time before your changes for nested mapping support)

Now, I've followed your guidelines and made it your way:

dataField: 'vendor.name'
nestedField: 'vendor'

tested it with my local ES instance of my project. Everyting works like a charm! Finally I do not need a patched reactivesearch, hooray! ;)

[aol-nnov]

~~@metagrover I've just noticed a weird thing: terms in MultiList are displayed fine, but if I tick one (or several) of them, results in the ResultCard are not filtered.

Any clue what I've missed? (It was working fine with my approach you reviewed yesterday)~~

Oh, please disregard this. It's me again. Everything is okay with this patch.

[metagrover]

Probably something's off with the defaultQuery. Check if the final query is being wrapped by nested query?

I'm looking into this!

[aol-nnov]

no need to.. It was me again ). I've updated the comment (strike through was not applied though)