You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for curly brackets when resolving envs (#2868)
<!-- Reference any GitHub issues resolved by this PR -->
Closes#2851
## Introduced changes
<!-- A brief description of the changes -->
- Added implementation for resolving environmental variables with curly
braces
## Checklist
<!-- Make sure all of these are complete -->
- [x] Linked relevant issue
- [x] Updated relevant documentation
- [x] Added relevant tests
- [x] Performed self-review of the code
- [ ] Added changes to `CHANGELOG.md`
---------
Co-authored-by: ddoktorski <[email protected]>
Co-authored-by: Franciszek Job <[email protected]>
Copy file name to clipboardExpand all lines: docs/src/projects/configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,7 +160,7 @@ the configuration from the local file will be used to override the global `defau
160
160
161
161
## Environmental Variables
162
162
163
-
Programmers can use environmental variables in both `Scarb.toml::tool::snforge` and in `snfoundry.toml`. To use an environmental variable as a value, use its name prefixed with `$`.
163
+
Programmers can use environmental variables in both `Scarb.toml::tool::snforge` and in `snfoundry.toml`. To use an environmental variable as a value, use its name either with or without curly braces, prefixed with `$` (e.g. `${MY_ENV}` or `$MY_ENV`).
164
164
This might be useful, for example, to hide node urls in the public repositories.
0 commit comments