-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Nested env variables do not get parsed #4865
Comments
I ran into this problem as well. I'm not sure what the idea behind it is, however I'm currently |
Closing as duplicate of #1736 |
I am wondering why this was closed as a duplicate of #1736 as this specifically pertains to how CYPRESS_* vars get parsed when setting CYPRESS_REPORTER_OPTIONS when #1736 pertains to deeply nested values in the plugins section? Have tested this in 4.11.0 when #1736 was merged in and using CYPRESS_REPORTER_OPTIONS from the command line is still a no go. |
For more complex configuration objects, you may want to consider passing a JSON.stringified object surrounded by single quotes.
module.exports = (on, config) => {
console.log(config) // see what all is in here!
// return config
return config
} |
Current behavior:
Cypress does not parse object env variables. Example:
This happens because the
getProcessEnvVars
function expects only string or boolean values:cypress/packages/server/lib/config.coffee
Lines 583 to 588 in 44c0416
cypress/packages/server/lib/util/coerce.js
Lines 10 to 18 in 44c0416
Expected behavior
Parse nested env variables, similar to what is done for args
cypress/packages/server/lib/util/args.js
Line 112 in 680a2fc
The text was updated successfully, but these errors were encountered: