-
Notifications
You must be signed in to change notification settings - Fork 10
[T2845] - Refactore "Suggested Donation amount" should be price based and not quantity based #240
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
base: 14.0-MyCompassion2.0
Are you sure you want to change the base?
[T2845] - Refactore "Suggested Donation amount" should be price based and not quantity based #240
Conversation
Summary of ChangesHello @SlWa99, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors the system for managing suggested donation amounts, transitioning from a fragile quantity-based calculation to a more robust price-based approach. Previously, donation suggestions were derived by multiplying a quantity by a product's base price, leading to inconsistencies when product prices changed. The updated system allows administrators to define fixed monetary donation amounts directly, ensuring stability and ease of management. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request successfully refactors the suggested donation amount logic from a quantity-based calculation to a direct price-based configuration. The changes are well-implemented across the model, controller, and view layers, improving maintainability. I've identified one area for improvement in the controller to ensure that configured donation amounts are always positive, preventing potential issues with zero or negative value donations.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Refactor of Suggested Donation Amounts
Problem Description
Suggested donation amounts were previously defined as quantities multiplied by a base product price.
This made price management fragile and error-prone when the product’s sale price changed.
Applied Changes
Model (product.template)
my_compassion_donation_amount_lowmy_compassion_donation_amount_mediummy_compassion_donation_amount_highBackend
Frontend
DonationFormComponent,DonationProductComponent) to display fixed amounts without multiplication logic._extract_donation_order_line_fields) to:price_unit1.0(product_uom_qty)Result
Administrators can now configure fixed donation amounts (e.g. 15 CHF, 50 CHF) independently of the product’s catalog price.