-
Notifications
You must be signed in to change notification settings - Fork 3.4k
rename cy.type disableSpecialChars options
#4761
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
Conversation
|
After discussion, we'll go ahead and keep this option but...
|
disableSpecialCharSequences options
disableSpecialCharSequences optionsdisableSpecialChars options
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.
- Can we say explicitly to "pass the option: { ... }" in the footer?
- Can we add a link to the
cy.typedocs in the footer too? https://on.cypress.io/type
|
I feel a little bit like....am I missing something? The default for I reversed all of the logic and booleans in this commit 159f1d0 |
|
@jennifer-shehane nice. good catch |
| const allChars = _.keys(Keyboard.specialChars).concat(_.keys(Keyboard.modifierChars)).join(', ') | ||
|
|
||
| expect(err.message).to.eq(`Special character sequence: '{bar}' is not recognized. Available sequences are: ${allChars}`) | ||
| expect(err.message).to.eq(`Special character sequence: '{bar}' is not recognized. Available sequences are: ${allChars} |
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.
Approving this PR but this would be a good place to introduce template tags using the common-tags module.
After discussion, we'll go ahead and keep this option but...
parseSpecialCharSequencescy.type()error message that indicates an invalid sequence and point the user to this optionclose #4287
close #4744
Docs
cy.type()renamedisableSpecialCharsopions cypress-documentation#1903