Skip to content
This repository has been archived by the owner on Jun 27, 2019. It is now read-only.

Adding explanation about uppercase env vars #195

Merged
merged 4 commits into from Dec 4, 2017

Conversation

BrunoBernardino
Copy link
Contributor

For when they're set with zapier env.

Relevant Trello Card

@@ -601,7 +601,7 @@ <h2 id="env">env</h2>
<div class="row-height">
<div class="col-md-5 col-sm-12 col-height docs-primary">
<blockquote>
<p>Read and write environment variables.</p>
<p>Read, write, and delete environment variables.</p>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently I forgot to npm run docs for another merged PR. 🙊

README-source.md Outdated
@@ -695,6 +695,8 @@ should('some tests', () => {

> This is a popular way to provide `process.env.ACCESS_TOKEN || bundle.authData.access_token` for convenient testing.

> **NOTE** Variables defined via `zapier env` will _always_ be stored and accessed in uppercase format.

Copy link
Member

@eliangcs eliangcs Dec 4, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be more specific by saying something like:

... will be uppercased. For example, you would access the variable defined by zapier env 1.0.0 foo_bar 1234 with process.env.FOO_BAR.

@BrunoBernardino
Copy link
Contributor Author

Alright, please check it out @eliangcs !

@BrunoBernardino BrunoBernardino merged commit 76c2ef8 into master Dec 4, 2017
@BrunoBernardino BrunoBernardino deleted the fix-explain-env-uppercase branch December 4, 2017 15:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants