Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Seeding Report: no logs in table, display a message #105

Open
braughtg opened this issue May 3, 2023 · 4 comments
Open

Seeding Report: no logs in table, display a message #105

braughtg opened this issue May 3, 2023 · 4 comments
Labels
UI/UX User Interface / User Experience Improvement

Comments

@braughtg
Copy link
Contributor

braughtg commented May 3, 2023

If there are no logs in the table then the filters, table, and summaries do not show up. The page where they should be is just blank. Instead we want there to be a message saying “There are no logs in the time range you have selected. Please select new dates.”

There are two scenarios when the filters, table, and summaries disappear. First is when there are no logs within the date range, the second is when the user deletes all the logs in the date range. This is likely due to there being no logs in the array seedingLogs.

To test this go to the Seedings Report subtab under BarnKit tab, which is on the home page.

NoLogsNeedMessageIssue


Issue by IrisSC
Friday Jul 23, 2021 at 17:56 GMT
Originally opened as DickinsonCollege/FarmData2#258

@braughtg braughtg added the UI/UX User Interface / User Experience Improvement label May 3, 2023
@braughtg
Copy link
Contributor Author

braughtg commented May 3, 2023

Also include Cypress tests that confirm the behavior.


Comment by braughtg
Wednesday Sep 01, 2021 at 13:20 GMT

@braughtg
Copy link
Contributor Author

braughtg commented May 3, 2023

I will start work on this


Comment by Batese2001
Thursday Sep 16, 2021 at 21:57 GMT

@braughtg
Copy link
Contributor Author

braughtg commented May 3, 2023

In order for the error message to display appropriately, that is, displaying once the results have been gathered and not while waiting for results to load, issue #272 should be solved first


Comment by Batese2001
Friday Sep 17, 2021 at 19:02 GMT

@braughtg
Copy link
Contributor Author

braughtg commented May 3, 2023

This is also related to #259 and #284. It might be easy to combine them and make a PR that solves both.


Comment by braughtg
Tuesday Sep 28, 2021 at 12:13 GMT

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
UI/UX User Interface / User Experience Improvement
Projects
None yet
Development

No branches or pull requests

1 participant