Add `unsafe-to-chain-command` exception for `type` and `clear` commands when used together

[fuxingloh]

According to the Cypress documentation on clear, it is considered a correct usage to chain the clear command with the type command, and vice versa:

cy.get('input[name="name"]').clear().type('Jane Lane')
cy.get('input[name="name"]').type('Jane Lane').clear()

As of v2.13.2, the current lint rule does not allow this usage.

[nagash77]

@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.

[websitevirtuoso]

yes. I just had to ingore this eslint rule. I have too many cases

  cy.getBySel('post.title').find('input').clear().type(newPost.title)

[dqiubread]

Any update on this change?

[corydeppen]

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?

[oracast]

it is dead. just move to playwright

[dqiubread]

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?

This PR should fix it but it hasnt been merged. https://github.com/cypress-io/eslint-plugin-cypress/pull/141/files
In the meantime my team decided to use patch-package with the changes in the PR to fix it.

[dqiubread]

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?

This PR should fix it but it hasnt been merged. https://github.com/cypress-io/eslint-plugin-cypress/pull/141/files In the meantime my team decided to use patch-package with the changes in the PR to fix it.

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.

[crfrolik]

According to the Cypress documentation on clear, it is considered a correct usage to chain the clear command with the type command, and vice versa:

cy.get('input[name="name"]').clear().type('Jane Lane')
cy.get('input[name="name"]').type('Jane Lane').clear()

As of v2.13.2, the current lint rule does not allow this usage.

I've found that cy.get('input[name="name"]').type('{selectall}Jane Lane') is normally an acceptable workaround for the first one.

[MikeMcC399]

@fuxingloh

You wrote quite a long time ago:

According to the Cypress documentation on clear, it is considered a correct usage to chain the clear command with the type command, and vice versa:

cy.get('input[name="name"]').clear().type('Jane Lane')
cy.get('input[name="name"]').type('Jane Lane').clear()
As of v2.13.2, the current lint rule does not allow this usage.

• PR update examples to have them follow unsafe to chain conventions cypress-documentation#6186 from May 2025, coming from @jennifer-shehane of the Cypress.io team, however corrected many of the examples on the https://docs.cypress.io/ site regarding unsafe-to-chain compliance, based on issue Clarify usage for commands marked as unsafe to chain further commands cypress-documentation#6185.

The API > Commands > clear now lists the following as correct usage:

cy.get('[type="text"]').clear() // Clear text input
cy.get('textarea').type('Hi!')
cy.get('textarea').clear() // Clear textarea
cy.focused().clear() // Clear focused input/textarea

and this no longer includes chaining .clear().type() or .type().clear().

Given this new information from the Cypress.io team, I'm closing the issue.