Skip to content

fix(site): show wsproxy errors in context in WorkspaceProxyPage #11556

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 3 commits into from
Jan 11, 2024

Conversation

johnstcn
Copy link
Member

@johnstcn johnstcn commented Jan 10, 2024

  • Shows the overall report error at the top of the page, if present.
  • Shows workspaceproxy errors above warnings inside the corresponding element, if present.

image

@johnstcn johnstcn self-assigned this Jan 10, 2024
@johnstcn johnstcn changed the title fix(site): WorkspaceProxyPage: show wsproxy errors in context fix(site): show wsproxy errors in context in WorkspaceProxyPage Jan 10, 2024
Comment on lines 149 to 151
{errors.map((error, i) => (
<span key={i}>{error}</span>
))}
{warnings.map((warning, i) => (
<span key={i}>{warning}</span>
))}
Copy link
Member Author

Choose a reason for hiding this comment

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

I tried turning this into an <ul> and playing around with list-style-type to prefix these with 🚫 or ⚠️ respectively, but this didn't seem to do what I wanted.

@johnstcn johnstcn requested a review from mtojek January 11, 2024 09:07
@johnstcn johnstcn force-pushed the cj/workspaceproxy-health-errors branch from 8cbb527 to 5c5e658 Compare January 11, 2024 09:52
Copy link
Member

@mtojek mtojek left a comment

Choose a reason for hiding this comment

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

Ship it!

@johnstcn johnstcn merged commit 8a12ee7 into main Jan 11, 2024
@johnstcn johnstcn deleted the cj/workspaceproxy-health-errors branch January 11, 2024 10:47
@github-actions github-actions bot locked and limited conversation to collaborators Jan 11, 2024
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.

2 participants