Skip to content
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

Merged
merged 150 commits into from
Oct 2, 2023

Conversation

riqwan
Copy link
Contributor

@riqwan riqwan commented Sep 27, 2023

No description provided.

pKorsholm and others added 30 commits September 6, 2023 15:05
@riqwan riqwan requested a review from adrien2p October 2, 2023 08:35
@riqwan riqwan changed the title Feat/pricing module methods feat(pricing,types): addPrice and removePricremoveRules APIs Oct 2, 2023
@riqwan riqwan changed the title feat(pricing,types): addPrice and removePricremoveRules APIs feat(pricing,types): addPrice and removePricreRules APIs Oct 2, 2023
Copy link
Member

@adrien2p adrien2p left a 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

}

const priceSets = await Promise.all(
data.map(async (d) => {
Copy link
Member

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

packages/pricing/src/services/pricing-module.ts Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants