-
Notifications
You must be signed in to change notification settings - Fork 6k
feat(extensions): add helper header above extensions search #2501
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
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.
Looks great!
lib/vscode/src/vs/workbench/contrib/extensions/browser/extensionsViewlet.ts
Outdated
Show resolved
Hide resolved
lib/vscode/src/vs/workbench/contrib/extensions/browser/extensionsViewlet.ts
Outdated
Show resolved
Hide resolved
lib/vscode/src/vs/workbench/contrib/extensions/browser/extensionsViewlet.ts
Outdated
Show resolved
Hide resolved
lib/vscode/src/vs/workbench/contrib/extensions/browser/extensionsViewlet.ts
Outdated
Show resolved
Hide resolved
Love the gif btw 🔥 |
dc2445c
to
7060f60
Compare
I’m not totally sure why the |
Ahh, sorry about the failed release step, it's my fault. I pushed a fix to master, please feel free to rebase. |
044d992
to
93ca456
Compare
Bump @nhooyr - ready for a second review |
@jsjoeio make sure to squash the really long Update file commits generated by github. |
Hmm! Good catch. Let me look into it. |
You got it! |
I’m having trouble figuring this out on iPad since I don’t have access to DevTools to inspect the styles 🤔 I’m looking at the Welcome page and don’t see anything jumping out at me. The links in the list have no classes so i’m not sure where the link color is coming from. The easiest solution would be to hard-code the link style to match the rest of code-server but I worry that wouldn’t work well across various themes. I’ll keep investigating. |
Well...hard-coding the color works. Not sure what else to try. Any thoughts/suggestions @nhooyr ? |
93ca456
to
3af5c25
Compare
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.
Happy to merge as is but one downside of hard coding the link color like we have is that the :visited
style doesn't take any affect and so the links don't turn purple anymore which sucks.
I understand @code-asher has some ideas to fix this?
Or one more I should say, like you said themes will also be a problem. So we can't merge as is then. |
Yeah exactly. I'll move this back to draft state then re-request a review when it's ready! |
Fixed the color issues (H/T to @code-asher for pointing me in the right direction) |
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.
perfecto!! 🔥
I noticed that :visited
isn't supported by any of VS Code's other UI links so it's fine that we don't here too.
Oh didn't even think about that - thanks for checking! Let's get this bad boy merged in! |
After i fix the lint issues :) |
720a268
to
9d67fa1
Compare
Add a short message above the search box on the Extensions panel. This helps explain the extension divergence to the user. If they click dismiss, it stores an item in localStorage to prevent the message from showing up on subsequent loads. Co-authored-by: Asher <ash@coder.com>
9d67fa1
to
500ba92
Compare
Add a short message above the search box on the Extensions panel. This helps explain the extension divergence to the user.
If they click dismiss, it stores an item in localStorage to prevent the message from showing up on subsequent loads.
Builds off the work previously done by @cmoog in #2185
Screenshots
And it uses the correct colors based on theme:
IMG_0042.MP4
Checklist
Fixes Add help information to the extension search view #2132