Skip to content
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

fix: edge cases during cy.type in number input #6033

Merged
merged 1 commit into from
Dec 23, 2019
Merged

Conversation

kuceb
Copy link
Contributor

@kuceb kuceb commented Dec 23, 2019

User facing changelog

  • bug fix: fixed regression in 3.8.0 during cy.type with non-number characters and {enter} special character.

Additional details

How has the user experience changed?

PR Tasks

  • Have tests been added/updated?
  • Has the original issue been tagged with a release in ZenHub?

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Dec 23, 2019

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

  • Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
  • Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

  • The feature/bugfix is self-documenting from within the product.
  • The change provides the end user with a way to fix their problem (no dead ends).

Functionality

  • The code works and performs its intended function with the correct logic.
  • Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
  • The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

  • The code is readable (too many nested 'if's are a bad sign).
  • Names used for variables, methods, etc, clearly describe their function.
  • The code is easy to understood and there are relevant comments explaining.
  • New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
  • There are comments containing link(s) to the addressed issue (in tests and code).

Quality

  • The change does not reimplement code.
  • There's not a module from the ecosystem that should be used instead.
  • There is no redundant or duplicate code.
  • There are no irrelevant comments left in the code.
  • Tests are testing the code’s intended functionality in the best way possible.

Internal

  • The original issue has been tagged with a release in ZenHub.

@cypress
Copy link

cypress bot commented Dec 23, 2019



Test summary

3589 0 47 0


Run details

Project cypress
Status Passed
Commit e27ea1c
Started Dec 23, 2019 4:34 PM
Ended Dec 23, 2019 4:39 PM
Duration 04:54 💡
OS Linux Debian - 9.11
Browser Multiple

View run in Cypress Dashboard ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

Copy link
Member

@jennifer-shehane jennifer-shehane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I confirmed this is working and fixes the failing cases in the issues. Tests cover these 2 cases. 👍

@kuceb kuceb changed the title fix 3.8.0 regressions for edge cases during cy.type in number inputs fix: edge cases during cy.type in number input Dec 23, 2019
@kuceb kuceb merged commit 16b76f4 into develop Dec 23, 2019
@@ -260,7 +260,11 @@ const shouldUpdateValue = (el: HTMLElement, key: KeyDetails, options) => {

if (!(numberRe.test(potentialValue))) {
debug('skipping inserting value since number input would be invalid', key.text, potentialValue)
options.prevVal = needsValue + key.text
if (key.text.match(/[-+eE\d\.]/)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this regexp should be hoisted to the top and given a variable name to help describe what it is

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also a description would be helpful

Comment on lines +484 to +486
if (!$elements.isInput(el)) {
$selection.replaceSelectionContents(el, '\n')
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a description of why this is necessary would be helpful here.

kuceb added a commit that referenced this pull request Dec 23, 2019
@kuceb kuceb mentioned this pull request Dec 23, 2019
brian-mann pushed a commit that referenced this pull request Dec 23, 2019
avallete pushed a commit to avallete/cypress that referenced this pull request Jan 8, 2020
Fix edge case introduced into cypress-io#6033 about typing invalid number

Fixes cypress-io#6055
jennifer-shehane added a commit that referenced this pull request Jan 10, 2020
Fix edge case introduced into #6033 about typing invalid number

Fixes #6055

Co-authored-by: Jennifer Shehane <[email protected]>
@emilyrohrbough emilyrohrbough deleted the fix-number-enter branch August 1, 2024 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants