Skip to content
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

Allow svgs in walkthroughs to be clickable #128581

Closed
Tracked by #128574
miguelsolorio opened this issue Jul 13, 2021 · 4 comments
Closed
Tracked by #128574

Allow svgs in walkthroughs to be clickable #128581

miguelsolorio opened this issue Jul 13, 2021 · 4 comments
Assignees
Labels
getting-started insiders-released Patch has been released in VS Code Insiders polish Cleanup and polish issue ux User experience issues
Milestone

Comments

@miguelsolorio
Copy link
Contributor

We previously talked about how it would be great if our SVGs could leverage links to open commands (like opening the extension marketplace) as the extension images in the walkthroughs look clickable:

CleanShot 2021-07-13 at 14 58 47@2x

@miguelsolorio miguelsolorio added ux User experience issues polish Cleanup and polish issue getting-started labels Jul 13, 2021
@miguelsolorio miguelsolorio added this to the July 2021 milestone Jul 13, 2021
@miguelsolorio
Copy link
Contributor Author

miguelsolorio commented Jul 14, 2021

Thanks for adding this @JacksonKearl! I was trying to update our svgs to start using this via:

<a xlink:href="command:extension.open?%5Bms-python.python%5D">
	<g filter="url(#filter1_d)">
		<rect x="236" y="316" width="48" height="48" rx="4" fill="white"/>
		<rect x="240" y="320" width="40" height="40" fill="url(#pattern1)"/>
	</g>
</a>

image

The command was provided by @sandy081 but it sounds like the extensionId argument is not being passed when debugged:

image

@JacksonKearl do you know why that would be? Other commands work fine but the ones with arguments don't

@JacksonKearl
Copy link
Contributor

JacksonKearl commented Jul 14, 2021

@misolori I believe you want "command:extension.open?%22ms-python.python%22", with %22's

This is: encodeURIComponent('"ms-python.python"'), whereas you have encodeURIComponent('[ms-python.python]').

@miguelsolorio
Copy link
Contributor Author

miguelsolorio commented Jul 14, 2021

Aha! Thank you! Looks like this command opens the extension in the extension detail view. Do we have a command to open this in the extensions view like:

CleanShot 2021-07-14 at 14 42 37@2x

EDIT: nvm, I believe it is command:workbench.extensions.search?%22ms-python.python%22 so I think I am good now. Thanks!

@miguelsolorio
Copy link
Contributor Author

This works 🥳🎉

CleanShot.2021-07-14.at.15.19.53.mp4

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
getting-started insiders-released Patch has been released in VS Code Insiders polish Cleanup and polish issue ux User experience issues
Projects
None yet
Development

No branches or pull requests

3 participants
@JacksonKearl @miguelsolorio and others