Skip to content

feat: add frontend for locked workspaces #8655

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

Merged
merged 16 commits into from
Aug 4, 2023
Merged

feat: add frontend for locked workspaces #8655

merged 16 commits into from
Aug 4, 2023

Conversation

sreya
Copy link
Collaborator

@sreya sreya commented Jul 21, 2023

No description provided.

@sreya sreya marked this pull request as ready for review August 1, 2023 16:35
@sreya sreya requested a review from BrunoQuaresma August 2, 2023 03:45
@@ -25,8 +25,8 @@ export const WorkspaceStatusBadge: FC<
return (
<ChooseOne>
{/* <ImpendingDeletionBadge/> determines its own visibility */}
<Cond condition={Boolean(ImpendingDeletionBadge({ workspace }))}>
<ImpendingDeletionBadge workspace={workspace} />
<Cond condition={Boolean(LockedBadge({ workspace }))}>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You probably don't need this since the LockedBadge is already doing the check and returning null if it should not be displayed.

setLockedWorkspaces([])
}
}, [experimentEnabled, data, filterProps.filter.query])

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This logic feels very similar to the useWorkspacesToBeLocked, why not use it here as well?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The useWorkspacesToBeLocked takes a template which the workspaces page doesn't mandate. I could refactor it, but I'd rather merge this as-is and go back and clean up things as we move it out of experimental.

Copy link
Collaborator

@BrunoQuaresma BrunoQuaresma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just minor comments but overall, it looks good to go 👍

@bpmct
Copy link
Member

bpmct commented Aug 2, 2023

/deploy-pr

@github-actions
Copy link

github-actions bot commented Aug 2, 2023

🚀 Deploying PR 8655 ...
⚠️ This deployment will be deleted when the PR is closed.

@sreya sreya merged commit e436083 into main Aug 4, 2023
@sreya sreya deleted the jon/lockedfe branch August 4, 2023 00:46
@github-actions github-actions bot locked and limited conversation to collaborators Aug 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants