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

Cypress.env's usage is not clear in the documentation #82

Closed
BrunoBernardino opened this issue Nov 16, 2015 · 4 comments
Closed

Cypress.env's usage is not clear in the documentation #82

BrunoBernardino opened this issue Nov 16, 2015 · 4 comments

Comments

@BrunoBernardino
Copy link

The example at https://github.com/cypress-io/cypress/wiki/env#no-arguments-usage shows the file like:

// cypress.json
{
  "env": {
    "foo": "bar",
    "baz": "quux"
  }
}

But that doesn't work. It should, in fact, be:

// cypress.json
{
  "cypress": {
    "env": {
      "foo": "bar",
      "baz": "quux"
    }
  }
}
@BrunoBernardino BrunoBernardino changed the title Cypress.env's use is not clear in the documentation Cypress.env's usage is not clear in the documentation Nov 16, 2015
@brian-mann
Copy link
Member

You are right. In the next version I'm going to automatically remove the nested cypress object from existing cypress.json. This has been on my todo list for about 8 months now, so it's time.

@BrunoBernardino
Copy link
Author

That would actually be better.

I imagine there will be backwards-compatibility so projects don't just start failing :)

@brian-mann
Copy link
Member

Yes, I'll write it to automatically migrate existing cypress.json to the new format so nothing breaks.

@brian-mann
Copy link
Member

Fixed in 0.12.4.

@cypress-io cypress-io locked as resolved and limited conversation to collaborators Dec 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants