Avoid misleading inline comments in .env example (#19708)
dotenv currently doesn't support inline comments (see https://github.com/motdotla/dotenv/issues/484), so it's misleading to use inline comments in documentation examples.
This commit is contained in:
parent
3766cff9b7
commit
7e387f0fce
1 changed files with 6 additions and 2 deletions
|
@ -63,8 +63,12 @@ export async function getStaticProps() {
|
|||
> ```bash
|
||||
> # .env
|
||||
> A=abc
|
||||
> WRONG=pre$A # becomes "preabc"
|
||||
> CORRECT=pre\$A # becomes "pre$A"
|
||||
>
|
||||
> # becomes "preabc"
|
||||
> WRONG=pre$A
|
||||
>
|
||||
> # becomes "pre$A"
|
||||
> CORRECT=pre\$A
|
||||
> ```
|
||||
|
||||
## Exposing Environment Variables to the Browser
|
||||
|
|
Loading…
Reference in a new issue