-
Notifications
You must be signed in to change notification settings - Fork 426
feat(elements,ui): Add support for loading actions #3927
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
Conversation
🦋 Changeset detectedLatest commit: 8223cd6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| </Card.Body> | ||
| <Card.Actions> | ||
| <Common.Loading> | ||
| <Common.Loading scope='submit'> |
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.
will need this added to each submit action across both sign in and signup. Not just the start step.
alexcarpenter
left a comment
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.
👍🏼 I can follow up with the usage implementation in the UI components.
Co-authored-by: Alex Carpenter <[email protected]>
Description
This PR adds support for actions, which are smaller states within a step. This allows us to disambiguate loading states within a single step. This PR adds support for the
passkeyandsubmitactions withinstart, but also lays the foundation for future actions within other steps. This allows us to show the correct busy state on the related UI element.Checklist
npm testruns as expected.npm run buildruns as expected.Type of change