THIS ISSUE IS A STUB AND NEEDS DECISIONS / REFINEMENTS
Task Description
VERIFY whether using one and the same component to render errors on the page level as well as in tighter error boundaries and even inside DataGrid is a good idea (take into account that inside DataGrid, also other states such as empty, loading would need to be rendered as well, or whether the latter should be rendered elsewhere.
Once that is verified, implement an Error(working title) component that can render the various error configurations as per our design. API TBD.
Error and States Visual Design
Sub-tasks
Additional Context
For the components, use the error titles and descriptions as per the table in the uxdocs as defaults.
THIS ISSUE IS A STUB AND NEEDS DECISIONS / REFINEMENTS
Task Description
VERIFY whether using one and the same component to render errors on the page level as well as in tighter error boundaries and even inside DataGrid is a good idea (take into account that inside DataGrid, also other states such as empty, loading would need to be rendered as well, or whether the latter should be rendered elsewhere.
Once that is verified, implement an
Error(working title) component that can render the various error configurations as per our design. API TBD.Error and States Visual Design
Sub-tasks
Additional Context
For the components, use the error titles and descriptions as per the table in the uxdocs as defaults.