We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we have the !expr method as used by yaml etc.
!expr
There are other options, like SPel (#{...}) and ${...} interpolation (runtime vs pre-run).
#{...}
${...}
https://cran.r-project.org/web/packages/GetoptLong/vignettes/variable_interpolation.html also allows ${...} and @{...}.
@{...}
For environment variables, allow .env and .Renviron read from the project dir or be listed as part of --file or --env-file
.env
.Renviron
--file
--env-file
See also:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently we have the
!expr
method as used by yaml etc.There are other options, like SPel (
#{...}
) and${...}
interpolation (runtime vs pre-run).https://cran.r-project.org/web/packages/GetoptLong/vignettes/variable_interpolation.html also allows
${...}
and@{...}
.${...}
for environment variables@{...}
(or#{...}
) for runtime (but unlike like!expr
): this would insert value into a character!expr
will override the whole prop, so can result in numeric etcFor environment variables, allow
.env
and.Renviron
read from the project dir or be listed as part of--file
or--env-file
See also:
The text was updated successfully, but these errors were encountered: