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

Support pattern in vsce commands #1012

Open
jdneo opened this issue Jul 9, 2024 · 2 comments
Open

Support pattern in vsce commands #1012

jdneo opened this issue Jul 9, 2024 · 2 comments
Assignees
Labels
feature-request Request for new features or functionality

Comments

@jdneo
Copy link
Member

jdneo commented Jul 9, 2024

Now, the vsce command like tool only support to specify the accurate file name to do tasks like publish.

vsce publish -i extension.vsix

I hope pattern match can be supported, like

vsce publish -i *.vsix
@benibenj
Copy link
Contributor

Could you provide a bit more context on why this would be helpful in your case?

@benibenj benibenj self-assigned this Jul 10, 2024
@benibenj benibenj added info-needed Issue requires more information from poster feature-request Request for new features or functionality labels Jul 10, 2024
@jdneo
Copy link
Member Author

jdneo commented Jul 10, 2024

Hi @benibenj,

In CI/CD pipelines, we run several commands towards vsce. Basically package, generate-manifest, publish.

If the command do not specify the output file name, the vsix file name will include the version number, which is dynamic. Things gets a little bit more complicated when it comes to the pre-release.

then it's not easy to specify the input file name for the following action like publish.

Though the problem can be addressed to add -o extension.vsix when packaging, but then I cannot easily see the version number, publisher and extension name from the file name.

@benibenj benibenj removed the info-needed Issue requires more information from poster label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants