Skip to content

fix: ensure that projects without optional chainer support can use @cypress/code-coverage #881

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

Merged
merged 4 commits into from
Sep 16, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix linter
  • Loading branch information
ryanthemanuel committed Sep 16, 2024
commit 92485cc6ea71f0d1363f6845960720aba46c04d6
2 changes: 1 addition & 1 deletion support.js
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ const registerHooks = () => {
// Note that we are purposefully not supporting the optional chaining syntax here to
// support a wide range of projects (some of which are not set up to support the optional
// chaining syntax due to current Cypress limitations). See:
// https://github.com/cypress-io/cypress/issues/20753
// https://github.com/cypress-io/cypress/issues/20753
if (win) {
applicationSourceCoverage = win.__coverage__
}
Expand Down
Loading