-
Notifications
You must be signed in to change notification settings - Fork 30.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
[@testing-library/cypress] Fix feedback from #37692 #38072
[@testing-library/cypress] Fix feedback from #37692 #38072
Conversation
👋 Hi there! I’ve run some quick performance metrics against master and your PR. This is still an experiment, so don’t panic if I say something crazy! I’m still learning how to interpret these metrics. Let’s review the numbers, shall we?
Wow, it looks like all the big movers moved in the right direction! Way to go! 🌟 If you have any questions or comments about me, you can ping |
@simjes Thank you for submitting this PR! 🔔 @aaronmcadam @ppi-buck @NoriSte @wKovacs64 @existentialism @airato - please review this PR in the next few days. Be sure to explicitly select If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead. |
@simjes The Travis CI build failed! Please review the logs for more information. Once you've pushed the fixes, the build will automatically re-run. Thanks! |
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.
This is awesome! So much better ❤️
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.
This looks great, @simjes. Thank you!
The linting will fail due to cypress-io/cypress#5065, any suggestions on how we can resolve this, or does it have to be resolved in the
cypress
package?
Is it possible to get this merged without lint passing, given it's an upstream issue with Cypress and TS 3.6, @sheetalkamat?
@simjes I haven't seen anything from you in a while and this PR currently has problems that prevent it from being merged. The PR will be closed tomorrow if there aren't new commits to fix the issues. |
@simjes To keep things tidy, we have to close PRs that aren't mergeable but don't have activity from their author. No worries, though - please open a new PR if you'd like to continue with this change. Thank you! |
I guess I'll keep an eye on cypress-io/cypress#5065 and reopen after it is solved @sheetalkamat |
I spoke with Gleb on Gitter and it sounds like the plan is to wait until they finish migrating to jQuery v3. It wasn't clear how far off that will be, but it's being worked on in cypress-io/cypress#1229. |
jQuery v3 was just merged, just waiting on a release now. |
@wKovacs64 sounds good, got updated PR ready. Will check tomorrow. |
New PR in #39394 |
Fixing feedback from #37692
The linting will fail due to cypress-io/cypress#5065, any suggestions on how we can resolve this, or does it have to be resolved in the
cypress
package?npm test
.)npm run lint package-name
(ortsc
if notslint.json
is present). This fails due to typings in the dependency to cypress, see Cypress + TypeScript 3.6.2 errors due to outdated JQuery types cypress-io/cypress#5065Select one of these and delete the others:
If changing an existing definition:
tslint.json
containing{ "extends": "dtslint/dt.json" }
. If for reason the any rule need to be disabled, disable it for that line using// tslint:disable-next-line [ruleName]
and not for whole package so that the need for disabling can be reviewed.