-
Notifications
You must be signed in to change notification settings - Fork 3
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
New Partner Detail UI with Tab View #1464
Conversation
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.
Overall looks good to me. I found a small shadow annoyance and commented on it.
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.
Please fix the shadow bug.
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.
LGTM! Waiting on @CarsonF's review to merge.
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.
Great start @adam-soltech! LMK if you have questions
src/scenes/Partners/Detail/Tabs/Projects/PartnerDetailProjectsTable.tsx
Outdated
Show resolved
Hide resolved
src/scenes/Partners/Detail/Tabs/Projects/PartnerDetailProjectsTable.tsx
Outdated
Show resolved
Hide resolved
src/scenes/Partners/Detail/Tabs/Projects/PartnerDetailProjectsTable.tsx
Outdated
Show resolved
Hide resolved
076efa6
to
66bdad2
Compare
82bc927
to
25583a8
Compare
25583a8
to
f681703
Compare
f681703
to
ad5b9d4
Compare
ad5b9d4
to
77e8ef1
Compare
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.
Thanks @adam-soltech!
Ticket
Design (I will be doing a separate review with product and design around this and have a few remaining questions for them)
Some thought that came up while doing this:
In these cases I defaulted to not trying to combine these components. Even though they share some attributes and combining them would be a bit more DRY, I've seen these types of abstractions (esp. with tables being passed wildly different configs) make a confusing mess very quickly.
I do think it might be good to abstract the partner profile card, or maybe a generic flat style card since they share the same styles and more or less the same functionality (edit the card fields), but wanted to defer to the team/Carson before getting too clever.