Extension divergence help information in the UI #2185
Conversation
ci/dev/vscode.patch
Outdated
| @@ -31,32 +31,6 @@ index f2ea1bd37010b1eb8a43ce9beaae4a88810f6e2d..3f660f9981921ec465d2b8809a1a5ea5 | |||
| const yarnrc = fs.readFileSync(path.join(REPO_ROOT, 'remote', '.yarnrc'), 'utf8'); | |||
| const target = /^target "(.*)"$/m.exec(yarnrc)[1]; | |||
| return target; | |||
| diff --git a/build/lib/extensions.js b/build/lib/extensions.js | |||
There was a problem hiding this comment.
Something went wrong with the diff here. I think you need to rebase your branch and clean.
There was a problem hiding this comment.
NOTE: code-server has it's own marketplace of open-source extensions due to
<a href="https://github.com/cdr/code-server/blob/master/doc/FAQ.md#differences-compared-to-vs-code" target="_blank">legal distribution restrictions</a>.
VSIX assets from the official marketplace can be
<a onClick="MAKE THIS EXECUTE THE UPLOAD VSIX COMMAND">uploaded<a/>.
Thoughts on something like this?
|
@kylecarbs I do think a link to the official marketplace is worth a lot. |
|
Oh yeah I'm down to include that. Just tryna reduce the size of the copy as much as possible. |
|
Possibly dumb question, is downloading extensions to use in
non-Microsoft products a TOS violation? That's the sense I had but I'm
no lawyer.
|
|
My nitpick here is use the same caution dialogue indicator used in Git when you're exceeding the 50-character limit so the user will see it immediately, it will add a sense of visual priority of what to read first. |
|
Hmm, that's an interesting idea, it looks like it pops up below the textbox as you type. I lean toward keeping the current method because that popup floats and would probably cover an extension or two in the search results which could be frustrating. We could only show it if there weren't any results, but I think having results but not the right ones might be a common case (just a guess though) and those cases would never get the help text. |
There was a problem hiding this comment.
Looks good to me. BTW if we still want to add a link for jumping directly to the upload we can do it with something like:
uploadButton.addEventListener("click", () => {
this.instantiationService.createInstance(InstallVSIXAction, InstallVSIXAction.ID, InstallVSIXAction.LABEL).run()
});
|
Closing this PR as it has become clear that linking to or referencing the existence of the official marketplace is a no-go. Suggesting users to upload via the dropdown has the same problem. Keeping the helper text without including instructions for resolution will cause more confusion than it's worth. Eventually, if we ever move to open-source our extension marketplace, an overlay of this nature will be appropriate. 😢 I'll open a new PR with a revised issue template for extension requests. |
Adds the following UI to the extension search view:
Closes #2132