vscode-cue: List in VSCode extension marketplace for .cue extension

[vsekhar]

Is it possible to list the extension in the marketplace without associating it with the .cue extension?

Searching the marketplace for just "cue" turns up 4 extensions only one of which is related to the .cue extension.

Would be great if this one was in that list (easier install, auto updates, etc.).

[cameronbraid]

From searching for other extensions, it appears that the marketplace can support multiple extensions that target the same file name extension

[betawaffle]

It's totally possible to add the extension to the marketplace with the .cue extension. The only reason it isn't listed yet is because I haven't had any time to figure out what I need to do to publish it, nor the time to actually publish it.

[cameronbraid]

Sure thing, I totally understand.

And by the way, thanks for the extension, I seem to go blind when my code is monochrome

[mattt]

@betawaffle Thank you for taking the time to write this plugin! Echoing what @cameronbraid said, programming with and without syntax highlighting for an unfamiliar language is like night and day.

For your consideration, this GitHub Action seems to provide a convenient way to automate publishing without much setup.

[vsekhar]

It's totally possible to add the extension to the marketplace with the .cue extension. The only reason it isn't listed yet is because I haven't had any time to figure out what I need to do to publish it, nor the time to actually publish it.

Updated issue title.

[myitcv]

Can someone who is more familiar with the VSCode Marketplace setup help me understand what is required here?

I'm very happy to help move this issue along, and improve discovery for the CUE project.

[johnallen3d]

I'd be willing to help get this going. I've been using a somewhat manual process with vsce to package/publish an extension. A couple of things to consider.

• use a manual or automated process
  • if manual, document the steps
  • if automated, what is the preferred triggering action (tag pushed, release PR merged, GitHub release created)?
• an organization based Personal Access Token (PAT) will need be needed
• consider keeping a CHANGELOG so that it's easier to publish release notes

[johnallen3d]

Regarding triggering an automated release. It looks like CUE is triggering releases on version tag push. That should be easy enough to replicate if that workflow is of interest.

[johnallen3d]

As a proof of concept, I've set up a release GitHub action on my cue fmt extension that's triggered on version tag push:

https://github.com/johnallen3d/vscode-cue-fmt/blob/2fd4555728a36bd5c49743d97aadca3d050f58f4/.github/workflows/release.yml

Here are the steps I'm following:

https://github.com/johnallen3d/vscode-cue-fmt/blob/2fd4555728a36bd5c49743d97aadca3d050f58f4/RELEASE.md

[RA80533]

@betawaffle, is there anything we can do to help? Is there anyone from the @cue-sh organization willing to assist with the initial steps of publishing the extension?

[tuxity]

Hello everyone, I have made a PR here with the instructions to make it work. Feel free to comment and give feedbacks! Thanks