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][FIX] delivery_postlogistics: fix date computation #745

Closed

Conversation

TDu
Copy link
Member

@TDu TDu commented Dec 20, 2023

If there is multiple commitment dates when creating a picking. Use the date the furthest in the future.

@TDu TDu force-pushed the 14-fix-postlogistics-delivery-fix-date branch from cecf50d to 462da11 Compare December 20, 2023 14:34
)

if order_commitment_date:
order_commitment_dates = [
Copy link
Member

@mmequignon mmequignon Dec 20, 2023

Choose a reason for hiding this comment

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

We have to consider the shipping_policy.
If all at once use max(), if asap use min()

Also, commitment date might be False in some cases. This isn't a mandatory field

>>> max([False, datetime.now()])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: '>' not supported between instances of 'datetime.datetime' and 'bool'

edit: I missed the if date in the comprehension list

@sebalix sebalix added the bug label Jan 2, 2024
@sebalix sebalix changed the title [14.0][FIX] postlogistics delivery fix date computation [14.0][FIX] delivery_postlogistics: fix date computation Jan 2, 2024
@rousseldenis
Copy link
Contributor

rousseldenis commented Mar 14, 2024

@TDu What's the status of this ?

Could you rebase ?

@rousseldenis rousseldenis added this to the 14.0 milestone Mar 14, 2024
If there is multiple commitment dates when creating a picking.
Use the date the furthest in the future.
@TDu TDu force-pushed the 14-fix-postlogistics-delivery-fix-date branch from 462da11 to b254c95 Compare March 15, 2024 12:16
@TDu
Copy link
Member Author

TDu commented Mar 15, 2024

@rousseldenis Rebase done. Status: it is being used, but need to investigate that comment.

Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 14, 2024
@github-actions github-actions bot closed this Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants