Debouncing impact on UX is more noticeable when TableData size is larger, such as when the TableData has greater than 8k entries, about 25mb. Adding debouncing reduces excessive rerenders of charts and pauses caused by processing when typing.
To test: change line 9 in data-portal/src/Analysis/AtlasDataDictionary/AtlasDataDictionaryTable/TestData/GenerateTableData.js to const numberOfEntries = 8000; then run Node GenerateTableData.js in that directory. Then run storybook with npm run storybook and use the mockedValidData selection for the story AtlasDataDictionaryLoading to compare and contrast the UX in this branch vs. master when typing in the search bar.
Changes to column headers and numeric formatting:
Improvements
Adds debouncing for search input on VADC Atlas Data Dictionary application to improve UX when typing searches with large table data sizes
Updates column names and formats numbers with commas to improve readability
Link to JIRA ticket if there is one: https://ctds-planx.atlassian.net/browse/VADC-1020
Developer Notes
Debouncing impact on UX is more noticeable when TableData size is larger, such as when the TableData has greater than 8k entries, about 25mb. Adding debouncing reduces excessive rerenders of charts and pauses caused by processing when typing.
To test: change line 9 in
data-portal/src/Analysis/AtlasDataDictionary/AtlasDataDictionaryTable/TestData/GenerateTableData.jstoconst numberOfEntries = 8000;then runNode GenerateTableData.jsin that directory. Then run storybook withnpm run storybookand use themockedValidDataselection for the story AtlasDataDictionaryLoading to compare and contrast the UX in this branch vs. master when typing in the search bar.Changes to column headers and numeric formatting:
Improvements