Skip to content

Add data aware filter controls to ItemTable #149

Open
campb303 opened this issue Dec 4, 2020 · 4 comments
Open

Add data aware filter controls to ItemTable #149

campb303 opened this issue Dec 4, 2020 · 4 comments
Assignees
Labels
feature-request Request for functionality that has not already been implemented handoff Issues that will not be fixed by the first webqueue2 team (after 7/16/21)

Comments

@campb303
Copy link
Collaborator

campb303 commented Dec 4, 2020

The react-table kitchen sink example shows data aware filters that allow interact with data in different ways better suited for each data type.

We should implement date range controls to allow easier filtering of dates in ItemTable.
Screen Shot 2020-12-04 at 12 29 02 PM

@campb303 campb303 added feature-request Request for functionality that has not already been implemented frontend labels Dec 4, 2020
@campb303 campb303 added this to the v1 milestone Dec 15, 2020
@campb303 campb303 assigned benne238, wrigh393 and campb303 and unassigned benne238 Jan 5, 2021
@wrigh393
Copy link
Collaborator

Material-UI's TextField component can be rendered with a native date picker but the documentation points out that native input controls support by browsers isn't perfect. The Material-UI lab has a specific DatePicker component but would require us to chose a date management library to manage dates.

There is a DateRangePicker component in the works but this is a part of the Material-UI X package, so we would need to add functionality ourselves.

@campb303
Copy link
Collaborator Author

We can use the following filter types per column:

Column Data Type Filter Control
Queue String Text Box
Item # String Text Box
Subject String Text Box
Priority String Text Box
Last Updated Date Object Date Range Picker
Department String Text Box
Building String Text Box
Date Received Date Object Date Range Picker

Date Picker Behavior:

State Behavior
Empty Show All
First date has a value, second date empty First date is a lower bound, no upper bound
First box is empty, second box has a value Not allowed
Both boxes have a value Inclusive bounded search

We may want to make the second box disabled unless the first box has a value.

@campb303 campb303 modified the milestones: v1-proof-of-concept, v2-production-ready-read-only Feb 5, 2021
@campb303 campb303 removed the frontend label Mar 17, 2021
@campb303
Copy link
Collaborator Author

campb303 commented May 5, 2021

This was briefly prototyped in its own branch without success. Need to revisit later.

@campb303 campb303 assigned campb303 and unassigned campb303 and wrigh393 Jul 6, 2021
@campb303 campb303 removed this from the production-ready-read-only milestone Jul 6, 2021
@campb303
Copy link
Collaborator Author

campb303 commented Aug 3, 2021

This will not be addressed by the current team.

@campb303 campb303 added the handoff Issues that will not be fixed by the first webqueue2 team (after 7/16/21) label Aug 3, 2021
Sign in to join this conversation on GitHub.
Labels
feature-request Request for functionality that has not already been implemented handoff Issues that will not be fixed by the first webqueue2 team (after 7/16/21)
Projects
None yet
Development

No branches or pull requests

3 participants