Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix List page display on dataProvider error #8319

Merged
merged 7 commits into from
Oct 28, 2022
Merged

Conversation

WiXSL
Copy link
Contributor

@WiXSL WiXSL commented Oct 27, 2022

Fixes #8241

  • Improve List view on error
  • Add a test

Before
before

After
after

@WiXSL WiXSL added the WIP Work In Progress label Oct 27, 2022
Copy link
Member

@fzaninotto fzaninotto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does it behave if the error comes after a successful render, e.g. at page 2?

@@ -70,7 +66,7 @@ export const ListView = <RecordType extends RaRecord = any>(
})
: children}
</Content>
{pagination !== false && pagination}
{error ? <PaginationLimit /> : pagination !== false && pagination}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you should say 'no results found' in case of error.

Copy link
Contributor Author

@WiXSL WiXSL Oct 27, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my latest commit, I've customized the PaginationLimit component to accept a message prop instead of being a dummy component

@WiXSL
Copy link
Contributor Author

WiXSL commented Oct 27, 2022

How does it behave if the error comes after a successful render, e.g. at page 2?

It shows the notification error, renders the empty "No results found" view for a blink and gets back to render the previous page

@@ -70,7 +66,11 @@ export const ListView = <RecordType extends RaRecord = any>(
})
: children}
</Content>
{pagination !== false && pagination}
{error ? (
<PaginationLimit message="ra.notification.data_provider_error" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It feels weird to me to render a component named 'pagination' here, since we don't even know if the data is supposed to be paginated or not.

I understand that the code of the component you want to display is very similar to the code of PaginationLimit, but to me they have different purposes, so they should be two different components (even if the code is duplicated).

Copy link
Contributor Author

@WiXSL WiXSL Oct 27, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about adding an Error component:
<Error error={error} resetErrorBoundary={null} />

error

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not too found of this solution either, cause we don't do it for other dataProvider errors, so why only do it for the list?

To me, the content of the PaginationLimit was enough for our needs (provided we change the message of course), but I just thought we should create a separate component for this use.

However, this Error component makes me realize it could be a welcome addition to add a 'Retry' button, that would call refresh from useRefresh. This could be useful in case it's only a temporary error.

What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of the Error page. Displaying an empty page with a warning is less user friendly IMHO.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alright then 😅

packages/ra-ui-materialui/src/list/List.spec.tsx Outdated Show resolved Hide resolved
@slax57
Copy link
Contributor

slax57 commented Oct 28, 2022

Okay for me!
I'll let @fzaninotto approve it as well before merging

@fzaninotto fzaninotto merged commit 221dcbd into master Oct 28, 2022
@fzaninotto fzaninotto deleted the fix-list-error-display branch October 28, 2022 12:36
@fzaninotto fzaninotto added this to the 4.5.0 milestone Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFR Ready For Review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

List show nothing when http error after upgraded to v4
3 participants