search

gitpod-samples / Gitpod-Raycast-Extension

Raycast Extension for Gitpod
MIT License
15 stars 6 forks source link

Request: Integrate with IDE options + Workspace Classes #17

Closed loujaybee closed 1 year ago

loujaybee commented 1 year ago

Did you know through the URL you can customise the editor, class and some other stuff?

Would be cool to be able to open a workspace through the raycast extension using these URL options.

You can see some of them here: https://github.com/gitpod-io/website/pull/3377/files

Have a play, maybe it could be integrated somehow? 😍

Palanikannan1437 commented 1 year ago

Hey @loujaybee, Ohh wow! This is amazing and a NEEDED ONE!! We certainly were thinking of adding this, thank you so much for pointing us to this 🧡🧡

This'll definitely be present in the next release along with "user preferences" to set a default IDE type within the raycast extension itself 🚀

Palanikannan1437 commented 1 year ago

@Siddhant-K-code, I tried it with the documentation added in this PR

  1. With showOptions=true https://gitpod.io/?showOptions=true&useLatest=true&editor=code-desktop&workspaceClass=g1-large#https://github.com/gitpod-io/website

    image

  2. With showOptions=false https://gitpod.io/?showOptions=false&useLatest=true&editor=code-desktop&workspaceClass=g1-large#https://github.com/gitpod-io/website

image

But as you could see, both show the same results, I effectively want to get to this page directly with showOptions=false ...instead we would want to directly get to this page....

image

Is this the intended behaviour for showOptions or am I missing out on something here 😅?

filiptronicek commented 1 year ago

I really like this suggestion. If the extension could also always remember the options you used[^1], it'd be even more efficient!

[^1]: I imagine this could be implemented as follows: when you open a context, the extension would store the settings used as the default settings for the repository, allowing the user to change it later. When you open another branch with different settings, it would also store it, so that you can have different options even for branches - if the branch config would be the same, it would default to the repository settings and if those are not available, then to the global ones.

Palanikannan1437 commented 1 year ago

Aha @filiptronicek , that's exactly what we're going forward with!! The things you suggested put things into picture in an even better way 🚀

Thank you so much for the feedback 🧡

This is what I've come up with after your suggestions and ideas!

  1. There'd be a global preference which the user would be asked to choose after login which would be the default preference for all the repositories and their contexts as well

  2. There'd be a preference at a repository level, which they can access by say (CMD + "w") or something similar or directly from the actions menu in Raycast

  3. There'd be a preference at a context level (for individual branches, repos and issues), which users can access and configure by say (CMD + "w") or something similar or directly from the actions menu in Raycast!

The preferences would cascade as you suggested i.e. a. If preferences are not set at a context level then preferences set at a repository level will be used

b. If preferences are not set at a repository level then preferences set at the global level will be used