-
Notifications
You must be signed in to change notification settings - Fork 59
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 domain settings for project dashboard #689
feat: add domain settings for project dashboard #689
Conversation
Thank you for opening this pull request! 🙌 These tips will help get your PR across the finish line:
|
@@ -166,7 +186,7 @@ export const ProjectDashboard: React.FC<ProjectDashboardProps> = ({ | |||
); | |||
return projectDomainAtributes; | |||
}, | |||
staleTime: Infinity, | |||
enabled: !!projectAttributesQuery.data, |
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.
The behaviour when the project settings error out is not clear. So we fetch projectDomainAttributes only once we have the upper level query.
@@ -206,9 +230,7 @@ export const ProjectDashboard: React.FC<ProjectDashboardProps> = ({ | |||
</Typography> | |||
<Typography variant="h5">{t('tasksTotal', numberOfTasks)}</Typography> | |||
</div> | |||
<WaitForQuery query={projectDomainAttributesQuery}> |
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.
Not sure what the best way to implement this is but ideal scenario we nest the for project attributes and project domain attributes.
I implemented this at a non-component level by disabling the projectDomainAttributes
query until we have the data for project attributes
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.
added some explanatory comments
d4186fb
to
338bca5
Compare
packages/console/package.json
Outdated
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "@flyteorg/console", | |||
"version": "0.0.8", | |||
"version": "0.0.9", |
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.
🙌
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
Signed-off-by: 4nalog <4nalog@protonmail.com>
b668295
to
c2bf77a
Compare
Congrats on merging your first pull request! 🎉 |
TL;DR
This PR adds support for showing project attributes and project domain attributes in the Project Dashboard for flyteconsole.
Type
Are all requirements met?
Complete description
Currently, there is no way for users to directly tell project attributes, project domain attributes. This PR adds support for showing project attributes and project domain attributes in the Project Dashboard for flyteconsole.
Note: We currently merge the project attributes with the project domain attributes in a single view. In future and as per designs, we will indicate separately global and project level domain settings so that users can see what changed
Tracking Issue
https://github.com/flyteorg/flyteconsole/issues/382
Follow-up issue
https://github.com/flyteorg/flyteconsole/issues/382