We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
windmill-react-ui
I updated the windmill-ui package on windmill-dashboard-react.
Components are not being animated on entrance.
It looks like modal and sidebar entrance is not animated as they should be, there's also no transition on the docs when you open the modal:
https://windmillui.com/react-ui/components/modal
Looks like downgrading back to 0.3.1 solves the issue.
The text was updated successfully, but these errors were encountered:
I tried to downgrade to 0.4.1 in order to use Alert, but the bug is present in that version too
Alert
Downgrading to 0.3.1 solved the problem like @muametgrooby mentioned and I created the alert component manually for the time being.
Sorry, something went wrong.
A workaround is to add a non-empty string on the appear attribute. <Transition show={isOpen} appear="_">
appear
<Transition show={isOpen} appear="_">
Not sure what's the issue could be typescript-related. But doing the above workaround allows enter transition to work. It seems
Warning: Failed prop type: Invalid prop `appear` of type `string` supplied to `Transition`, expected `boolean`.
for the CSSTransition library. I think their documentation is faulty.
No branches or pull requests
windmill-react-ui
version: 0.5.0What you did:
I updated the windmill-ui package on windmill-dashboard-react.
What happened:
Components are not being animated on entrance.
Problem description:
It looks like modal and sidebar entrance is not animated as they should be, there's also no transition on the docs when you open the modal:
https://windmillui.com/react-ui/components/modal
Suggested solution:
Looks like downgrading back to 0.3.1 solves the issue.
The text was updated successfully, but these errors were encountered: