Originally intended as an alternative solution for #339
Some config fields, e.g. Username, Agent, ... support environment variables, such as $SSH_AUTH_SOCK. The user in the original issue had the extension on multiple devices with different operating systems, where VS Code settings are synced. Wanting to use $SSH_AUTH_SOCK on Mac and pageant for Agent got a bit tricky.
This feature is to add a combination of the following sub-features:
Support bash shell parameter expansion. This would allow e.g. ${SSH_AUTH_SOCK:-pageant} where an unset/empty $SSH_AUTH_SOCK would result in it giving pageant instead.
Support a simple version of Angular expressions. For this, ${code} would actually be an expression that gets evaluated, where referencing global variables result in the related environment variable or undefined instead.
Add some meta-variables, such as: $PLATFORM, $HOST, $USER, ... (availability depends on the field + would need a defined order)
Add an "analyzer" to the Settings UI that would analyze these expressions, check for syntax errors, and display what it would currently evaluate to (as much as is possible).
Originally intended as an alternative solution for #339
Some config fields, e.g.
Username,Agent, ... support environment variables, such as$SSH_AUTH_SOCK. The user in the original issue had the extension on multiple devices with different operating systems, where VS Code settings are synced. Wanting to use$SSH_AUTH_SOCKon Mac andpageantforAgentgot a bit tricky.This feature is to add a combination of the following sub-features:
${SSH_AUTH_SOCK:-pageant}where an unset/empty$SSH_AUTH_SOCKwould result in it givingpageantinstead.${code}would actually be an expression that gets evaluated, where referencing global variables result in the related environment variable or undefined instead.$PLATFORM,$HOST,$USER, ... (availability depends on the field + would need a defined order)