-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix: Revert cypress.json changes #15499
Conversation
Thanks for taking the time to open a PR!
|
config: _.cloneDeep(settings), | ||
envFile: _.cloneDeep(envFile), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only code changes besides the reverting.
it('clones settings and env settings, so they are not mutated', function () { | ||
const settings = { foo: 'bar' } | ||
const envSettings = { baz: 'qux' } | ||
|
||
this.setup(settings, envSettings) | ||
|
||
return config.get(this.projectRoot) | ||
.then(() => { | ||
expect(settings).to.deep.equal({ foo: 'bar' }) | ||
expect(envSettings).to.deep.equal({ baz: 'qux' }) | ||
}) | ||
}) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New test to make sure cypress settings don't get mutated.
nice. @chrisbreiding do you think we should squash+rebase this into three commits (two reverts, one bugfix) and do a merge commit? it would be nice to have the explicit revert commits in develop |
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
43eb3d5
to
4886f23
Compare
4886f23
to
496e458
Compare
User facing changelog
cypress.json
when adding the project IDAdditional details
This was caused by a combination of using
require
to obtain the contents ofcypress.json
and mutating the config object itself. Since node caches required modules, it mutated the in-memory cache of thecypress.json
, so subsequent 'reads' had the mutated content with extra values, which then got written back to the file when writing the project ID.This reverts PRs #15444 and #15263.
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?