-
Notifications
You must be signed in to change notification settings - Fork 69
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
Hook up "No Transactions" view #97
Comments
This will be best served by the empty table component: https://woocommerce.github.io/woocommerce-admin/#/components/packages/table?id=emptytable-component for a message lets use "No transactions to display" |
@reykjalin As you said and as @LevinMedia has pointed out, we may want the columns and other heading / controls – so we can render the table and then the |
@dechov @allendav Should we be including that in resolving this issue, or would that be a different issue? Specifically, changing from a Also, since |
@reykjalin Hm, I'm not sure. The table designs don't look to me like they are necessarily |
I'm starting to think the best way is to just add a summary saying "No transactions to display" if the table is empty, like this: @LevinMedia @dechov Let me know whether this ^ would work. I think the most consistent/obvious way to approach this would be to add something along the lines of an I can have this look sort of the same using an
EDIT 23:00 UTC June 28: That said, I don't know if this fits with @LevinMedia's (and others?) design, so I think this might be a question best answered by them 🙂 . |
The only EmptyTable usage right now in wc-admin is on the dashboard leaderboard areas. @LevinMedia if you come up with a desired behavior for this across all tables, let me know and we can update report tables to match in wc-admin. |
I defer to @LevinMedia, especially on how far upstream to take it, but the appearance looks right to me. I'm not sure if the missing features in the empty state are a big deal – but I actually didn't realize those features (incl. search, download, etc.) were on TableCard, not Table, so I guess we shouldn't give up TableCard as easily as I was suggesting :-) |
Yeah I think that looks great.
That seems like a reasonable approach to me! Sounds like it's inline with what @timmyc mentioned above too:
I'll sketch up a design for that first thing tomorrow (Monday July 1) |
As discussed in #97 using the summary property instead of an 'EmptyTable' component looks more consistent than using just the 'EmptyTable'. This has the caveat of using the summary for two purposes: displaying a message when there is no data available to display, and then displaying an actual summary when there _is_ data to display. This requires some boolean logic that I tried to make expressive so it's easy to follow.
As discussed in #97 using the summary property instead of an 'EmptyTable' component looks more consistent than using just the 'EmptyTable'. This has the caveat of using the summary for two purposes: displaying a message when there is no data available to display, and then displaying an actual summary when there _is_ data to display. This requires some boolean logic that I tried to make expressive so it's easy to follow.
@reykjalin I added an empty state to the transactions page in figma The row height with the message is the same as a normal table row: 60px The text styles for the empty table message should match the empty message style in the chart component: cc @timmyc If we're going to make these changes in the When a table is empty we're not being very consistent with what remains visible in the table header - I'd like to update it so that everything that's visible when table data is present is still visible in the empty state, it's just disabled. The exception to that rule being the kebab menu that allows users to toggle columns on and off. That should still be functional even when there's no data. Header elements that are disabled when the table is empty: Compare button (when applicable) Header elements that are always functional: Kebab that controls which columns are visible |
If you could make an issue on the wc-admin repo that would be |
Just going to ping @LevinMedia here, since I don't see an issue or PR in wc-admin related to this, and I'm unsure if that's because I can't find it, or if @LevinMedia missed this message. |
@reykjalin, I made an issue to track on wc-admin side woocommerce/woocommerce-admin#2613 |
As discussed in #97 using the summary property instead of an 'EmptyTable' component looks more consistent than using just the 'EmptyTable'. This has the caveat of using the summary for two purposes: displaying a message when there is no data available to display, and then displaying an actual summary when there _is_ data to display. This requires some boolean logic that I tried to make expressive so it's easy to follow.
As discussed in #97 using the summary property instead of an 'EmptyTable' component looks more consistent than using just the 'EmptyTable'. This has the caveat of using the summary for two purposes: displaying a message when there is no data available to display, and then displaying an actual summary when there _is_ data to display. This requires some boolean logic that I tried to make expressive so it's easy to follow.
As discussed in #97 using the summary property instead of an 'EmptyTable' component looks more consistent than using just the 'EmptyTable'. This has the caveat of using the summary for two purposes: displaying a message when there is no data available to display, and then displaying an actual summary when there _is_ data to display. This requires some boolean logic that I tried to make expressive so it's easy to follow.
As per the discussions in #120 this has been made (sort of) redundant for now. An empty table will now leave the default message Eventually the If we get to the point where the
@allendav it might make sense to move this issue to another milestone? I'll leave that up to you. |
Hi folks, I was thinking of picking up this issue as my 2nd "good first issue". Looks like adding a prop to the |
Presently the empty table renderers with the default message Screenshot with default message on route Screenshot with custom message on route We can discuss if there is a requirement to pass a custom message as of now, then we have to make changes to the IMO it would be a "good to have", not sure about the requirement of this feature at this moment. Or if the present default message works for us, we can close this issue and re-open if the need arises. cc @LevinMedia |
I think the current present default message works - thanks @naman03malhotra ! |
I'm not sure what's going on with the "undefined transactions" displayed in the footer. I've seen that from time to time, but I thought it was limited to the loading state. Would you mind creating a new issue so we can look into that @naman03malhotra? What would you expect to be displayed there @LevinMedia? "0 transactions $0 total $0 fees $0 net", something like that? Or omitted entirely? |
@jrodger I observed this issue as well, though it occurs intermittently. Initially, I thought there was a problem with my local setup, but doesn't look like it. I'll create an issue for the same and look into it. Thank you for confirming this! For now, I am closing this issue as per the comment. #97 (comment) |
When there are no transactions available to the display, present something meaningful instead of an empty table.
cc @LevinMedia for a mock
Child of #82
The text was updated successfully, but these errors were encountered: