-
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
Buttons bottom sheet & code coherence #395
Labels
Comments
B3nz01d
added
🧩 enhancement
New feature or request
🔍 triage
A new issue that needs to be treated
📱 demo app
⚛️ Component
labels
Jan 5, 2023
paulinea
added a commit
that referenced
this issue
Jan 16, 2023
…sistent with the code implementation
paulinea
added a commit
that referenced
this issue
Jan 16, 2023
paulinea
added a commit
that referenced
this issue
Jan 16, 2023
florentmaitre
pushed a commit
that referenced
this issue
Jan 16, 2023
…sistent with the code implementation
florentmaitre
pushed a commit
that referenced
this issue
Jan 16, 2023
florentmaitre
pushed a commit
that referenced
this issue
Jan 16, 2023
florentmaitre
pushed a commit
that referenced
this issue
Jan 16, 2023
florentmaitre
pushed a commit
that referenced
this issue
Jan 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the sprint demo, and within the buttons component the wording between the code keywords and the customization bottom sheet should be coherent.
The "enabled" parameter should be used both in the code and in the customization bottom sheet to be coherent.
The text was updated successfully, but these errors were encountered: