| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Description
- Implementation sometimes conflicts with Inventory search requirements/implementation
- Development due to these conflicts makes Browse implementation painful with numerous defects
- Challenges will be even greater as we implement additional Browse options
Goal
Propose an approach to update Inventory Search and Browse implementation that will support a more streamline implementation, scalability, and performant.
Spike results
...
There are two ways to separate Search and Browse: keep both in Inventory app and implement a toggle to switch between the two, and create a separate Inventory Browse module.
But before we go into that it will be useful first to get an overview of current implementation to see how the code is structured.
Current implementation
The main bulk of code is located in <InstacesList> component: https://github.com/folio-org/ui-inventory/blob/master/src/components/InstancesList/InstancesList.js
...
The resulting implementation will roughly consist of the red and green blocks separated into two separate components, and a third component will contain common code. I'd also suggest to implement them as functional components and use hooks to further separate business logic and presentation.
The two approaches
...
1. Toggle between Search and Browse
PPT slide deck that outlines proposed UI changes:
https://docs.google.com/presentation/d/1PSJyA9g9j1xmDpH8JymdLyxqeXxfoLZX23VZ-1dsx0w/edit#slide=id.p
...