-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
feat: Create product category flow #7034
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
9880175
to
245df44
Compare
245df44
to
97cb27b
Compare
97cb27b
to
67e3dca
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.
LGTM, but I didn't review the tests since the diff is impossible :)
import { StepResponse, createStep } from "@medusajs/workflows-sdk" | ||
|
||
type CreateProductCategoryStepInput = { | ||
product_category: CreateProductCategoryDTO |
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.
Typically we accept an array for the input, should we do the same here? Or is there a reason we can't?
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.
The product category service + repository will need a makeover to allow for bulk operations. This is a pretty comprehensive change, so I decided to open this PR now and then we can address the bulk support in a follow-up PR.
packages/medusa/src/api-v2/admin/product-categories/query-config.ts
Outdated
Show resolved
Hide resolved
…into feat/product-categories
f435961
to
83f5b19
Compare
Yeah, I am not sure we can do it any differently when converting the test suites. As long as the V1 tests are still passing without any changes, I think we should be fine. |
What