Hi! I found this article very helpful, but for some reason I faced an issue when adding the code to the support/index.js file... Cypress was telling me that there was no override for that option... I figured that probably I needed to change something in the Cypress core code to allow it to identify the custom key in the cypress.json file. So what I did was adding the hideXHR key to my "env": { } section, and then in the code instead of
Hi, I'm Sam and I'm an advocate for quality software. I'm a Cypress Ambassador and I work as the QA Lead at Pointivo where we're digitizing real-world infrastructure for analysis and maintenance.
If you're placing the config inside your env object, then yes that's necessary. I keep my config flag outside of the env object, in the main e2e config object. I believe it's optional where you keep it, as long as both pieces of code match.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi! I found this article very helpful, but for some reason I faced an issue when adding the code to the support/index.js file... Cypress was telling me that there was no override for that option... I figured that probably I needed to change something in the Cypress core code to allow it to identify the custom key in the cypress.json file. So what I did was adding the hideXHR key to my "env": { } section, and then in the code instead of
I put
And it worked as expected
Thanks!
If you're placing the config inside your
envobject, then yes that's necessary. I keep my config flag outside of theenvobject, in the maine2econfig object. I believe it's optional where you keep it, as long as both pieces of code match.