-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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(pricing,types): addPrice and removePricreRules APIs #5237
Conversation
…x.ts Co-authored-by: Riqwan Thamir <[email protected]>
Co-authored-by: Riqwan Thamir <[email protected]>
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, strong works guys, few comments here and there
packages/pricing/integration-tests/__fixtures__/price-set/index.ts
Outdated
Show resolved
Hide resolved
} | ||
|
||
const priceSets = await Promise.all( | ||
data.map(async (d) => { |
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.
yes I see what you mean, indeed having an id from the start would be the easiest way to do it. for that we could have a service method that only create the entities without persisting. Then adding @onInit on the before create would take care of assigning the id automatically when manager.create is called. Maybe this is something we can think of in another iteration unless you think it would be quick to do. Let me know what you think about it.
ps: this might be a too early optimisation but just want your takes on it for the future if we fall into it
No description provided.