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

fix: respect LAUNCH_EDITOR env rather than forcing 'code' as default #401

Closed
wants to merge 5 commits into from

Conversation

Smef
Copy link
Contributor

@Smef Smef commented May 23, 2024

The user's LAUNCH_EDITOR env is being overwritten by the default launchEditor option. If no launchEditor option is specified it should default to the LAUNCH_EDITOR env value. Currently if launchEditor is not specified, the option is set to "code" and the user's LAUNCH_EDITOR setting is ignored.

This change will respect the user's LAUNCH_EDITOR env by default if no launchEditor option is specified.

This also allows an arbitrary string as a valid launchEditor type, which is a valid option for launch-editor and is needed for custom launch scripts or when editors are installed in non-standard locations.

This fixes #369

Copy link

netlify bot commented May 23, 2024

Deploy Preview for vue-devtools-docs canceled.

Name Link
🔨 Latest commit a79c7ef
🔍 Latest deploy log https://app.netlify.com/sites/vue-devtools-docs/deploys/664f6da8e67d4500087c9572

@Smef
Copy link
Contributor Author

Smef commented May 23, 2024

It looks like the type is correct here, but needs to be changed upstream as well. I'll submit a PR there, too.

PR submitted: webfansplz/vite-plugin-vue-inspector#96

@webfansplz
Copy link
Member

Thanks for the PR, fixed in 561726d

@webfansplz webfansplz closed this May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: LAUNCH_EDITOR env support
2 participants