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

[14.0][ADD] stock_restrict_by_planned_consumed_date #1509

Open
wants to merge 3 commits into
base: 14.0
Choose a base branch
from

Conversation

petrus-v
Copy link
Contributor

@petrus-v petrus-v commented Feb 20, 2024

based on #1724 to avoid product reservation if expiration lot is before the expected consumed date

@petrus-v petrus-v force-pushed the 14.0-add-stock_restrict_by_planned_consumed_date branch from d6c0428 to d4ddd3e Compare February 20, 2024 14:41
@petrus-v petrus-v changed the title 14.0 add stock restrict by planned consumed date [14.0][ADD] stock restrict by planned consumed date Feb 20, 2024
@petrus-v petrus-v changed the title [14.0][ADD] stock restrict by planned consumed date [14.0][ADD] stock_restrict_by_planned_consumed_date Feb 20, 2024
@petrus-v petrus-v force-pushed the 14.0-add-stock_restrict_by_planned_consumed_date branch from d4ddd3e to b5eeb51 Compare February 20, 2024 21:07
Comment on lines 18 to 19
or quant.lot_id
and quant.lot_id.expiration_date > planned

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion,nitpick: Maybe add parenthesis to clearly separate the or and the and?

@petrus-v petrus-v force-pushed the 14.0-add-stock_restrict_by_planned_consumed_date branch from b5eeb51 to 11fe34b Compare June 26, 2024 16:36
@petrus-v petrus-v force-pushed the 14.0-add-stock_restrict_by_planned_consumed_date branch from 11fe34b to 8f87ddb Compare September 19, 2024 12:26
@rousseldenis rousseldenis added this to the 14.0 milestone Sep 19, 2024
Copy link

@alexandregaldeano alexandregaldeano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment on lines +17 to +18
or quant.lot_id
and quant.lot_id.expiration_date >= planned
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
or quant.lot_id
and quant.lot_id.expiration_date >= planned
or (
quant.lot_id
and quant.lot_id.expiration_date >= planned
)

Comment on lines +1 to +2
This module avoid to reserve goods if the planned consumed date by
the customer is after expiration time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This module avoid to reserve goods if the planned consumed date by
the customer is after expiration time.
This module avoids to reserve goods having an expiration time prior to the customer's planned consumed date.

Comment on lines +1 to +3
* Today we restrict expiration lot date must be greater thant planned consumed date in
some circumstance we probably want something flexible based on product configuration and
probably based on use_date (best before).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Today we restrict expiration lot date must be greater thant planned consumed date in
some circumstance we probably want something flexible based on product configuration and
probably based on use_date (best before).
* Today we restrict the reservation based on the lot expiration date, but in
some circumstances we probably want something configurable to base the restriction on `use_date` (best before).

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.

4 participants