-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
feat: add user action component #4088
feat: add user action component #4088
Conversation
4a35308
to
0e08cb9
Compare
@davehakkens / @dalibormrska - Thoughts on updating the label for the sign-up buttons on the doc list pages? |
onearmy-community-platform Run #6817
Run Properties:
|
Project |
onearmy-community-platform
|
Branch Review |
pull/4088
|
Run status |
Passed #6817
|
Run duration | 05m 42s |
Commit |
de81f4dedf: feat: add UserAction across app
|
Committer | Ben Furber |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
1
|
Pending |
0
|
Skipped |
0
|
Passing |
79
|
View all changes introduced in this branch ↗︎ |
39aea26
to
2c0e91d
Compare
Makes sense, I think I missed this case to think it through there in the figma file. I would just suggest using consistent language - Sign up to add your project |
ca8bebf
to
121fcd4
Compare
121fcd4
to
de81f4d
Compare
🎉 This PR is included in version 2.30.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR Checklist
PR Type
What kind of change does this PR introduce?
What is the new behavior?
A little util component to wrap around actions logged in user can do. Useful prep for #4044.
Reduces components that access the user store.
One small user change:
Does this PR introduce a DB Schema Change or Migration?
Git Issues
Closes #4079