ReactiveSearch and ReactiveMaps are fully compatible with React 18.x and above with the 4.x releases. This release comes after the feedback we have gathered from the iterative deployment of reactivesearch in production for the dozens of our clients over the last year. In this version, we have changed the way certain props behave, and included new components. This guide will give you a brief about all the changes.

ReactiveSearch

Removal of FE query generation

In this release we have removed the front-end query generation, we discourage the use of front-end queries to search backend which is a security risk. We're using the declarative Reactivesearch API to query the search backend. You can either self-host the OSS version of Reactivesearch API Server or use the Appbase services.

Removal of DataSearch & CategorySearch components

In 3.x we had two components for auto-suggestions, DataSearch & CategorySearch (to display category suggestions). In 4.x we have only one component named SearchBox to implement auto-suggestions UI.

v3.x:

Copy 
    <DataSearch
        componentId="Search"
        dataField={['title', 'description']}
    />

v4.x:

Copy 
    <SearchBox
        componentId="Search"
        dataField={['title', 'description']}
    />

Removal of Deprecated props

We have also removed the following deprecated props:

Prop Name

Component

Alternative
analyticsConfig ReactiveBase reactivesearchAPIConfig
appbaseConfig ReactiveBase reactivesearchAPIConfig
analytics ReactiveBase reactivesearchAPIConfig.recordAnalytics
enableAppbase ReactiveBase _
triggerAnalytics ReactiveList.renderItem triggerClickAnalytics
aggregationField All Components distinctField