-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add unsafe-to-chain-command
exception for type
and clear
commands when used together
#132
Comments
@fuxingloh , Thank you for submitting your feature request. Cypress Product Managers will review this request and consider it for future implementation. Please remember we cannot guarantee this will be implemented in a specific timeframe or at all. Please see the Cypress App Product Roadmap for what we currently have in the works. |
yes. I just had to ingore this eslint rule. I have too many cases
|
Any update on this change? |
It's been a year since this was reported. Can a maintainer at least confirm that this is something that needs to be addressed in the plugin or if the docs aren't completely accurate and the plugin is reporting correctly? |
it is dead. just move to playwright |
This PR should fix it but it hasnt been merged. https://github.com/cypress-io/eslint-plugin-cypress/pull/141/files |
Sorry just realized this is on type and clear command chaining and not the chaining custom commands to other commands. My team decided to just un chain them. |
According to the Cypress documentation on clear, it is considered a correct usage to chain the
clear
command with thetype
command, and vice versa:As of
v2.13.2
, the current lint rule does not allow this usage.The text was updated successfully, but these errors were encountered: