-
Notifications
You must be signed in to change notification settings - Fork 7
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
Version 1.0.2 #27
Version 1.0.2 #27
Conversation
[Progress] [Tooltip] Making props with default values optional
Upgrade to next.js 12.1, npm upgrade
Linting is failing due to a bug in eslint-plugin-react that is a dependency of eslint-plugin-next. Fixed in the canary version of eslin-plugin-next. I'd recommend waiting for 12.1.1. release instead of doing resolutions magic here. The changes here are not urgent and no harm is done by waiting for the eslint-plugin-next release |
pass missing testid
replace existing timepicker with MUI timepicker
eslint-plugin-next upgraded to v12.1.2 in this PR Should fix the linting issues |
Upgrade dependencies with npm upgrade and npm outdated
[Dialog][Button] Fix Dialog close button, pass props to IconButton
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.
Looks good and nice description on what has been done! 🎉
d696d39
🌡️ Progress and Tooltip component props optional, uses defaults
color
,type
andvariant
props for the Progress component are now optional and use default values if no prop is passed.arrow
prop for the Tooltip is now optional and uses the default value of true when the prop is not passed.New TimePicker component
Upgrading dependencies
Fixes
data-testid
to Select component when usingmultiple
prop (pass missing testid #28 )