Repository navigation
Feature/v0.4.2/environment variables - #53
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Environment variables
This PR introduces improvements to the developer experience:
1. Environment variables option
We now have an environment variable option
env_variables. By default, sandboxes don't have access to your .env file. With this option, you can select variables from your .env and make them available inside your sandbox.2.
envAPI for TypeScriptfsisn't available in the sandbox for TypeScript. So we provide anenvAPI to read environment variables declared in the options.Available methods:
env.get(key)— Get a specific environment variable (returnsundefinedif not found)env.has(key)— Check if an environment variable existsenv.getAll()— Get all environment variables as an object