We want to extend the <SearchAndSort> API such that you pass in the stripes configuration object from the application's package file, and the component figures out what parts to use. It will then no longer be necessary to pass in a bunch of other parameters, and those can eventually be deprecated.
Once this is done, we should eventually be able to dispose of the following properties:
initialPath
moduleName
moduleTitle
baseRoute
initialFilters
Environment
None
Potential Workaround
None
Checklist
hide
TestRail: Results
Activity
Show:
Zak Burke March 7, 2018 at 4:30 AM
Implemented across versions v1.4.3 (which accepted props.packageInfo as an alternative to some existing props) and v1.4.4 (which required props.packageInfo and deprecated the props that are now derived from it).
We want to extend the
<SearchAndSort>API such that you pass in thestripesconfiguration object from the application's package file, and the component figures out what parts to use. It will then no longer be necessary to pass in a bunch of other parameters, and those can eventually be deprecated.This is gradually becoming more urgent because of code like https://github.com/folio-org/ui-search/blob/477cab996d3484a3c619cd7e1ffd15a75a54a26b/src/Search.js#L223-L227 which we want to avoid duplicating across all the different modules.
Once this is done, we should eventually be able to dispose of the following properties:
initialPath
moduleName
moduleTitle
baseRoute
initialFilters