Skip to content

[18.0][MIG] sale_specific_order_date: Migration to 18.0#715

Open
deeniiz wants to merge 3 commits into18.0from
18.0-mig-sale_specific_order_date
Open

[18.0][MIG] sale_specific_order_date: Migration to 18.0#715
deeniiz wants to merge 3 commits into18.0from
18.0-mig-sale_specific_order_date

Conversation

@deeniiz
Copy link
Copy Markdown
Collaborator

@deeniiz deeniiz commented Sep 22, 2025

No description provided.

Copilot AI review requested due to automatic review settings September 22, 2025 11:26
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR migrates the sale_specific_order_date module from a previous version to Odoo 18.0. The module allows preserving a specific order date when it's defined in a quotation during order confirmation.

Key changes:

  • Added new module structure for Odoo 18.0 compatibility
  • Implemented _prepare_confirmation_values() method to preserve order date
  • Added build system configuration with pyproject.toml

Reviewed Changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
File Description
__manifest__.py Module metadata with version 18.0.1.0.0 and basic dependencies
models/sale_order.py Core functionality to preserve order date during confirmation
models/__init__.py Module import structure
__init__.py Main module initialization
pyproject.toml Build system configuration using whool
README.rst Module documentation and usage information

@deeniiz deeniiz requested a review from eantones September 22, 2025 12:46
@deeniiz deeniiz force-pushed the 18.0-mig-sale_specific_order_date branch from e79ce08 to 88151f9 Compare September 22, 2025 13:18
@deeniiz deeniiz force-pushed the 18.0-mig-sale_specific_order_date branch 3 times, most recently from 11b8906 to 937ea1d Compare October 21, 2025 12:52
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 8, 2026

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 label Mar 8, 2026
@eantones eantones added no stale and removed stale labels Mar 8, 2026
@deeniiz deeniiz force-pushed the 18.0-mig-sale_specific_order_date branch from 937ea1d to 9a5ff8a Compare March 12, 2026 11:06
@deeniiz deeniiz force-pushed the 18.0-mig-sale_specific_order_date branch from 9a5ff8a to 5eeb713 Compare March 12, 2026 11:07
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 12, 2026

Codecov Report

❌ Patch coverage is 54.54545% with 5 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (18.0@4b294fd). Learn more about missing BASE report.

Files with missing lines Patch % Lines
sale_specific_order_date/models/sale_order.py 44.44% 5 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             18.0     #715   +/-   ##
=======================================
  Coverage        ?   54.54%           
=======================================
  Files           ?        3           
  Lines           ?       11           
  Branches        ?        2           
=======================================
  Hits            ?        6           
  Misses          ?        5           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

3 participants