We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
gruntConfig = { env: { //dynamically created. chrome: { CAPS: [] } } }; grunt.registerTask('test:sauce:' + key, ['env:' + key + ':CAPS']);
I dynamically create the above config for grunt-dev but when later I wanna grab the CAPS in my test file, I realize that it is empty.
CAPS
Why is that? When I set the gruntConfig.env
When I wanna get the gruntConfig.env
The text was updated successfully, but these errors were encountered:
Any updates on this?
This is happening because you are not deep extending the object in the following code chunk:
function add(value, key) { if (process.env[key]) return grunt.log.writeln(key + ' already exists, leaving unchanged.'); var data = {}; data[key] = value; _.extend(process.env, data); }
Sorry, something went wrong.
This is expected behavior outside of grunt-env. Environment variables are strings only, so your array is being toString()ed into an empty ""
""
I'll add this as a reminder in the readme.
No branches or pull requests
I dynamically create the above config for grunt-dev but when later I wanna grab the
CAPS
in my test file, I realize that it is empty.Why is that?
When I set the gruntConfig.env
When I wanna get the gruntConfig.env
![screen shot 2014-04-25 at 10 27 25](https://cloud.githubusercontent.com/assets/6009583/2798674/a6e64d02-cc53-11e3-9c9d-b011d3fefb5f.png)
The text was updated successfully, but these errors were encountered: