-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: add treecluster list #38
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
{clusters.length === 0 ? ( | ||
<li className="text-center text-dark-600 mt-10"> | ||
<p> | ||
Keine Ergebnisse mit den eingestellten Filteroptionen gefunden. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if there is no data, e.g. on first use? Then the user sees this information and may be confused?
Suggestion: Maybe check in the condition if a filter (when the filter logic is back) is active. If so, display this message, otherwise display another message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point 👍
@@ -0,0 +1,14 @@ | |||
export enum Region { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should move this to the backend. But for now we can leave it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add this as a note to the issue 👍
@@ -0,0 +1,14 @@ | |||
export enum WateringStatus { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, we should move this to the backend
refs #26