-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Add product management description #34961
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
| const product: Product = yield apiFetch( { | ||
| path: `${ WC_PRODUCT_NAMESPACE }/${ productId }`, | ||
| path: addQueryArgs( `${ WC_PRODUCT_NAMESPACE }/${ productId }`, { | ||
| context: 'edit', |
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.
context is important for the returned data type as the default view context formats returned data in a way that is not ideal for editing.
Allowing context to be changed would better, but I think we can forego that since this data store will most likely be replaced with the CRUD data store generator in the near future.
Test Results SummaryCommit SHA: 9fed06b
To view the full API test report, click here. To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
plugins/woocommerce-admin/client/products/sections/product-details-section.tsx
Show resolved
Hide resolved
plugins/woocommerce-admin/client/products/sections/product-details-section.tsx
Show resolved
Hide resolved
plugins/woocommerce-admin/client/products/sections/product-details-section.tsx
Show resolved
Hide resolved
|
Thanks for the review, @mdperez86! I think you made some good suggestions here. I attempted several of them, but noted how they might negatively impact performance and introduce bugs to the current experience. It might be worth us exploring whether or not we should internally parse blocks back and forth to html instead of the consumers handling this. I'll post this to Slack soon to get some more discussion around this. I think a lot of these suggestions are still useful and worth exploring, but since this PR does not need those features, I'd recommend we open up follow-up issues to try and implement some of those enhancements. What do you think? |
bc4589d to
af30df8
Compare
03930d9 to
fef29c1
Compare
New hook, template, or database changes in this PRNew hooks:
|
|
Hi @joshuatf, thanks for merging this pull request. Please take a look at these follow-up tasks you may need to perform:
|
|
Cool update but how about:
in the description? Thanks |
All Submissions:
Changes proposed in this Pull Request:
Adds a description field to the new product management experience.
Also adds
contextto the API request to fix up returned response data.New editor:

Old editor:

How to test the changes in this Pull Request:
Products -> Add new (MVP)Other information:
pnpm --filter=<project> run changelog add?FOR PR REVIEWER ONLY: