-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Add shipping dimensions image #34857
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
Test Results SummaryCommit SHA: 6205b8a
To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
5864af4 to
4af0451
Compare
81a6ebc to
e732942
Compare
e732942 to
4da2d7d
Compare
4da2d7d to
db4037d
Compare
joshuatf
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.
This is looking great and testing well! Left a couple minor nitpicky naming comments, but pre-approving.
| { /* Side A */ } | ||
| <path | ||
| d="M10.4922 134.221V35.2617C10.4922 33.8539 11.9079 32.8867 13.2193 33.3986L98.3109 66.6076C99.0711 66.9043 99.5748 67.633 99.5837 68.449L100.703 171.089C100.719 172.534 99.2449 173.518 97.9167 172.95L11.7054 136.06C10.9695 135.745 10.4922 135.022 10.4922 134.221Z" | ||
| fill={ highlight === 'A' ? '#F0F6FC' : '#F6F7F7' } |
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.
Love this really simple solution; nicely done!
| export const ProductShippingSection: React.FC = () => { | ||
| const { getInputProps } = useFormContext< Product >(); | ||
| const { formatNumber, parseNumber } = useProductHelper(); | ||
| const [ highlightSide, setHighLightSide ] = |
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.
Nitpicky, but should be setHighlightSide. ("Highlight" being one word)
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.
Absolutly ;)
| </p> | ||
| <div className="product-shipping-section__container"> | ||
| <div> | ||
| <div className="product-shipping-section__dimensions__body"> |
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.
We typically use a similar class naming style to BEM so this class could either be:
product-shipping-section__dimensions-body
Or if dimensions is its own standalone block:
product-shipping-section-dimensions__body
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.
Done
joshuatf
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.
Looks great! Thanks for the updates!
|
Hi @mdperez86, thanks for merging this pull request. Please take a look at these follow-up tasks you may need to perform:
|
All Submissions:
Changes proposed in this Pull Request:
Partialy closes #34329.
How to test the changes in this Pull Request:
Screen.Recording.2022-09-28.at.10.54.42.AM.mov
Other information:
pnpm --filter=<project> run changelog add?FOR PR REVIEWER ONLY: