-
Notifications
You must be signed in to change notification settings - Fork 0
feat: add main pages #9
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
Conversation
…or improved readability and functionality
…oved visibility and functionality
…directly into AppsRoute with refetch indicator
…s for improved data handling
…orkerpools routes
… rendering and data handling
…a handling and pagination
…rpools to assure next page in pagination
PierreJeanjacquot
left a comment
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.
Small bug on the pagination and filename casing issue.
Maybe an optimisation is possible on next pages detection to discuss (now or later).
Plus I have a few TS errors that prevent the production build to succeed, it may be worth addressing these ASAP to avoid later stress for deployment.
…pps, datasets, deals, tasks, and workerpools
…kerpools routes with alerts
…kerpools routes with hasPastError flag
|
With the latest commits, I introduced the variable hasPastError, which allows me to maintain the error state between refreshes. |
PierreJeanjacquot
left a comment
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.
still npm run build is failing
No description provided.