-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
DatePicker: Write tests and refactor #194
Comments
hi! can i work on this? |
@luckened For sure! Feel free to drop questions here if you need anything 🚀 |
@luizbaldi please take a look 🔍 |
@luckened great work! We have to decide on some things tho and modify couple of things in the DatePicker that were not well planned from the beginning (which is my fault).
This should be a minor change in code. I think we need to change
|
@arturbien thanks for the feedback! ❤️ |
Is this task completed, or is further testing and accessibility capability being added of value still? |
The
DatePicker
component is already created and it's functional, but it was written some time ago and it can be refactored (migrating from class-based to hooks). In order to achieve a good result, we also need a good test coverage.Running storybook locally
npm i
on the root folder)npm start
, this will start a local server and opens a tab on your browser automaticallysrc/DatePicker/DatePicker.stories.js
file in order to make it appearDatePicker.spec.js
file on the same folder to write testsAditional information
We're using React Testing Library to unit test our components and we have a good test coverage, so you can rely on the existing ones.
Before start working on this bug leave a comment here so we can avoid more than one person working on the issue, if you have any doubts feel free to drop a comment here or join us at Slack 🕺
The text was updated successfully, but these errors were encountered: