-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Fix: Workspace settings page design #5804
Conversation
@Julesssss Ready to merge. |
Will get to this tomorrow, ran out of time today. |
I think @Beamanator will take care of this now. |
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.
Code LGTM. Didn't get a chance to run, but this is on my list for tomorrow if it hasn't yet been merged.
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.
Tests well! Only 2 tiny comments
children: () => {}, | ||
user: {}, | ||
reimbursementAccount: {}, | ||
footer: null, |
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.
NAB; I think it could be nice to alphabetize these props or put them in the order they appear in propTypes
. What do you think?
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.
Usually, we keep the capital case for props that are a Component but here I am passing an element.
so if we want to use the footer as <Footer>
then it will make more sense.
So, I think this is fine.
Co-authored-by: Alex Beaman <dabeamanator@gmail.com>
@Julesssss This is ready. |
tested today, looking good. Will leave the merge to @Beamanator as he's yet to approve. |
I'm going to merge, so that we can get this N6 improvement in as soon as possible. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @Julesssss in version: 1.1.8-10 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.1.10-2 🚀
|
Details
Proposal => #5767 (comment)
Fixed Issues
$ #5767
Tests | QA Steps
Tested On
Screenshots
Web | Desktop
Mobile Web
iOS
Android