Skip to content
New issue

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

Protect against env vars not being set #12

Open
colearendt opened this issue Dec 26, 2019 · 2 comments
Open

Protect against env vars not being set #12

colearendt opened this issue Dec 26, 2019 · 2 comments

Comments

@colearendt
Copy link

Related to #11

If the proper env vars are not set, we should have apps, Rmds, etc. exit with a friendly error message to be clear that more configuration is necessary, because otherwise the proper actions can be a bit difficult for users to grok from the error messages.

@slopp
Copy link

slopp commented Dec 30, 2019

I wonder if this could be a feature of the markdown or config package; it seems like this conditional error message is helpful, and silly that we are copying the same code everywhere.

@colearendt
Copy link
Author

I like that idea a lot. required_env_vars as a YAML config or something... at simplest, we could always just write a helper function that does it for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants