Add error Snackbar to table components

[xplato]

Depends on #504 and #514

[razor-x]

Any thoughts on how to trigger a loading error in a story? Maybe we need a workspace on the fake that always returns errors on get / list?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
react	🛑 Canceled (Inspect)		Oct 3, 2023 5:17pm

[xplato]

Any thoughts on how to trigger a loading error in a story? Maybe we need a workspace on the fake that always returns errors on get / list?

@razor-x an erroring workspace isn't a bad idea. How would you go about that?

[razor-x]

We can just add a DB method to the fake to configure some behavior, like db.simulateInternalServerError('/devices/list', { workspace_id })

@seveibar I know you have thought about this, did you ever have a particular API in mind?

[seveibar]

@razor-x that pattern seems ok, although id always suggest documenting specific known bugs or scenarios when making simulation endpoints. In this case its not a bug we're replicating in the fake and the function is unlikely to cover up a bug (if it was repurposed) so i think its good!

[razor-x]

That makes sense. In this case the error is a generic issue that could be caused by anything. But we could name it simulateTemporaryOutage following your suggestion @seveibar

[razor-x]

We need a way to test this on storybook before we can merge it to make sure it renders correctly over the components.

[xplato]

@razor-x I believe this PR should be all unblocked now. Did some local testing and your recent fix seems to have patched up all the issues I had previously.