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

use empty string to "unset" variables #263

Merged
merged 1 commit into from
Oct 28, 2022
Merged

use empty string to "unset" variables #263

merged 1 commit into from
Oct 28, 2022

Conversation

mkhl
Copy link
Contributor

@mkhl mkhl commented Oct 23, 2022

the memento1 and environment variable collection2 apis
don't support "unsetting" variables,
only deleting them from the collection,
which leads to those variables being left along.
this change uses the empty string instead.
posix calls this value "null" for environment variables,
and it's technically different from the variable being unset
but the closest we can get.

the memento[1] and environment variable collection[2] apis
don't support "unsetting" variables,
only deleting them from the collection,
which leads to those variables being left along.
this change uses the empty string instead.
posix calls this value "null" for environment variables,
and it's technically different from the variable being unset
but the closest we can get.

[1]: https://code.visualstudio.com/api/references/vscode-api#Memento
[2]: https://code.visualstudio.com/api/references/vscode-api#EnvironmentVariableCollection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant