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

[Order] allow passing custom-attributes from price rules to order-item #2555

Merged
merged 13 commits into from
Mar 18, 2024

Conversation

dpfaffenbauer
Copy link
Member

Q A
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Fixed tickets #2532

@EinShoppo this is not ready yet, but the basic idea behind what we discussed. The idea is to allow passing custom attributes from pricing calculation to be stored in the order, thus using them to affect price calculation from cart-price-rules. (or basically anything cart-item-related). WDYT?

It is still missing parts like persistence of attributes or the cart-price-rule-condition to not allow non-discountable.

@dpfaffenbauer dpfaffenbauer added this to the 4.1.0 milestone Feb 18, 2024
@dpfaffenbauer dpfaffenbauer self-assigned this Feb 18, 2024
@dpfaffenbauer
Copy link
Member Author

@EinShoppo rest is now implemented as well

# Conflicts:
#	.github/workflows/behat.yml
#	.github/workflows/behat_ui.yml
#	.github/workflows/packages_bundles.yml
#	.github/workflows/packages_components.yml
#	.github/workflows/static.yml
#	docs/03_Bundles/Resource_Bundle/02_Pimcore_Entities.md
@dpfaffenbauer
Copy link
Member Author

@EinShoppo do you wanna give this a test?

@EinShoppo
Copy link

@dpfaffenbauer: Sounds great! One of my colleagues and I are looking at this today. I think you'll get feedback from us tomorrow at the latest.

@EinShoppo
Copy link

@dpfaffenbauer We finished our tests and it works like a charm! Big cheers and many thanks 👍
I really like the fact that the attribute is added to the cart price rules validation automatically, because i think that this attribute should win in any case and so it's good that you don't have to set a condition manually.

A possible improvement would be to also check for the presence of the not-discountable attribute in the product price rules, but this is probably technically more difficult to implement. So you can see it more as an idea for the future.

@dpfaffenbauer
Copy link
Member Author

@EinShoppo nice :). Ok, then we can merge this into the 4.1 branch. you then have to update your project to 4.1 to use that ok?

@EinShoppo
Copy link

@dpfaffenbauer We planed to update to 4.0 before, so this shouldn't be a big problem for us. Do you already know when it will be released?

@dpfaffenbauer
Copy link
Member Author

@EinShoppo probably after Pimcore Inspire. Are you faster than that?

@EinShoppo
Copy link

@dpfaffenbauer: I'm not sure, but if necessary we'll have to temporarily fork or patch the 4.0 version.

@dpfaffenbauer
Copy link
Member Author

@EinShoppo let's have a chat next week and discuss that, can you contact me directly?

@CLAassistant
Copy link

CLAassistant commented Mar 15, 2024

CLA assistant check
All committers have signed the CLA.

@dpfaffenbauer dpfaffenbauer merged commit 8c900b9 into coreshop:next Mar 18, 2024
276 checks passed
@dpfaffenbauer dpfaffenbauer deleted the custom-attributes branch March 18, 2024 13:23
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.

None yet

3 participants