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 leading number being trimmed on point type #376
Fix leading number being trimmed on point type #376
Conversation
Codecov Report
@@ Coverage Diff @@
## master #376 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 12 12
Lines 376 385 +9
Branches 109 111 +2
=========================================
+ Hits 376 385 +9
Continue to review full report at Codecov.
|
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.
Solid! Thank you 👏
@all-contributors please add @lourenci for code and tests |
I've put up a pull request to add @lourenci! 🎉 |
Thanks so much for your help! I've added you as a collaborator on the project. Please make sure that you review the |
🎉 This PR is included in version 12.0.5 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Thank you so much for this. I'll try to help the community as much as I can. My next step is to become a member of the @testing-library org. 😊 Thank you. |
What:
It solves #360.
How:
In the actual code handling the point, I concatenate the input's previous value.
I tried to keep the changes as little as possible once I'm not used to neither to the events nor to the lib.
Checklist: