Keep records in store while fetching

[seancolsen]

Current behavior

• Before fetching records, we clear all the existing records replacing them with dummy records just so that each cell displays a loading skeleton.
• In the Record Selector, we're auto-sizing the column widths based on the content of the cells.
• The combination of the above two strategies produces some funky loading behavior in the Record Selector. While searching, the table gets too narrow because the cells no longer have content. Then when the search is complete, the table gets wide again. This causes the UI to jump around which can be disorienting to users.

Desired behavior

• Don't wipe the records out until we have already fetched them. Maintain a separation of concerns between the records data and the records fetch status.
• We can still display loading skeletons on the cells by reacting to the fetch status.

[seancolsen]

Here's another reason why we shouldn't clear the records while fetching... If something goes wrong during the fetch, you might end up with this:

Here, I had this tab open on the staging site, but my session expired. I pressed the "Refresh" button within the UI. Now I lost my view of that data just because the refresh failed.

[seancolsen]

This issue came up again as a UX problem during a discussion on how to handle filtering on partially-entered dates.

[github-actions]

This issue has not been updated in 90 days and is being marked as stale.