-
Notifications
You must be signed in to change notification settings - Fork 975
Support :? shell syntax for variable substitution #4190
Copy link
Copy link
Open
Labels
area:configurationRelated to configuring the SDKRelated to configuring the SDKsig-issueA specific SIG should look into this before discussing at the specA specific SIG should look into this before discussing at the specspec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec labeltriage:accepted:ready-with-sponsorReady to be implemented and has a specification sponsor assignedReady to be implemented and has a specification sponsor assigned
Description
Metadata
Metadata
Assignees
Labels
area:configurationRelated to configuring the SDKRelated to configuring the SDKsig-issueA specific SIG should look into this before discussing at the specA specific SIG should look into this before discussing at the specspec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec labeltriage:accepted:ready-with-sponsorReady to be implemented and has a specification sponsor assignedReady to be implemented and has a specification sponsor assigned
Type
Projects
Status
Spec - Accepted
What are you trying to achieve?
Config WG merged a proposal (#3744, #3974, #3948) to support env var expansion syntax with defaults, using the traditional shell syntax
VARNAME:-default. But shell syntax also commonly includesVARNAME:?error messagesyntax for undefined variables which was omitted. This omission is an unexpected behavior to users who are used to shell syntax.Additional context.