8000 chore: some renames and just moving help links into own component by oxaudo · Pull Request #15640 · artsy/force · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: some renames and just moving help links into own component #15640

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

Merged
merged 4 commits into from
May 30, 2025

Conversation

oxaudo
Copy link
Member
@oxaudo oxaudo commented May 30, 2025

Changes here are mostly cosmetic to fix some unclear naming and move some code into own component so that it's easier to do responsive stuff.

@oxaudo oxaudo requested a review from erikdstock May 30, 2025 14:29
@oxaudo oxaudo self-assigned this May 30, 2025
Copy link
relativeci bot commented May 30, 2025

#2983 Bundle Size — 8.92MiB (~+0.01%).

2441e5b(current) vs 921a975 main#2982(baseline)

Warning

Bundle contains 18 duplicate packages – View duplicate packages

Bundle metrics  Change 3 changes Regression 1 regression
                 Current
#2983
     Baseline
#2982
Regression  Initial JS 3.6MiB(~+0.01%) 3.6MiB
No change  Initial CSS 0B 0B
Change  Cache Invalidation 43.87% 38.85%
No change  Chunks 103 103
No change  Assets 106 106
Change  Modules 5820(+0.03%) 5818
No change  Duplicate Modules 527 527
No change  Duplicate Code 3.98% 3.98%
No change  Packages 271 271
No change  Duplicate Packages 17 17
Bundle size by type  Change 1 change Regression 1 regression
                 Current
#2983
     Baseline
#2982
Regression  JS 8.78MiB (~+0.01%) 8.78MiB
No change  Other 144.14KiB 144.14KiB

Bundle analysis reportBranch oxaudo/shipProject dashboard


Generated by RelativeCIDocumentationReport issue

@@ -26,7 +28,7 @@ export const Order2DetailsPaymentInfo: React.FC<Props> = ({ order }) => {

return (
<Box p={2} backgroundColor="mono0">
<Text variant="sm" fontWeight={500} color="mono100">
<Text variant="sm" fontWeight={700} color="mono100">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't (think) we ever explicitly set the fontWeight like this; rather its just fontWeight='bold'

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea - we were looking at it and bold might work as well but it's 800 weight. 700 looks better in this context. Not a strong opinion though.... It works either way.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah... Never mind. Double checking the spec - and 700 is Bold. Will update:)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool thanks @oxaudo 👍 Regarding figma -- best to lean more closely to existing code patterns, vs careful analysis of the figma since sometimes designers don't exactly align to our design sys. Only reason I flagged this was because i've never seen a numeric fontWeight used before! So it felt like a snowflake addition, even if it might be technically specific in the Figma file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm maybe my fault, i did this the same way on checkout because i was copying css values from figma designs.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps easier said than done, but would always encourage eye-balling visual stuff and implementing by hand vs any direct copy / paste interaction with Figma. Palette is simple enough, and most things are just looking at the text variant and noticing spacing / margins / paddings. (again, easier said than done tho 😄)

@oxaudo
Copy link
Member Author
oxaudo commented May 30, 2025

Looks like this:
Screenshot 2025-05-30 at 12 40 55 PM

@oxaudo
Copy link
Member Author
oxaudo commented May 30, 2025

Merging this update so we can see latest on staging.

@oxaudo oxaudo merged commit 2ddfb56 into main May 30, 2025
11 checks passed
@oxaudo oxaudo deleted the oxaudo/ship branch May 30, 2025 18:23
@artsy-peril artsy-peril bot mentioned this pull request May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0