8c76a16366
Replace em-dashes and en-dashes with hyphens across 789 shipped source files (py/xml/js/scss) so the delivered module reads as human-written; em-dashes had become a recognizable AI-generated tell. Internal .md dev notes are excluded. The WO-sticker mojibake strippers keep their dash search targets (now written — / –). No logic changes: comments and display strings only; validated with py_compile + lxml parse. Rewrite the 7 customer notification emails to be intake-neutral (ship-in / drop-off / pickup) and repair-aware, and fix the Shipped email documents line (packing slip vs bill of lading; certificate only when issued). Subjects use a hyphen separator. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
22 lines
865 B
Python
22 lines
865 B
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
"""Drop the redundant ``revision_number`` Integer column on fp.part.catalog.
|
|
|
|
The model historically carried two revision fields:
|
|
* ``revision`` (Char, required) - the customer's actual revision label
|
|
* ``revision_number`` (Integer) - an internal counter
|
|
|
|
The Integer counter duplicated information already in ``revision`` and
|
|
got out of sync whenever the customer used a non-numeric scheme
|
|
(A/B/C, A1/A2, "ECO-2024-014" etc.). This migration drops the column.
|
|
``action_create_revision`` and the auto-rev path on 3D-model upload now
|
|
use ``_bump_revision_label`` which best-effort bumps the alphanumeric
|
|
label and lets the user adjust to the customer's actual scheme.
|
|
"""
|
|
|
|
|
|
def migrate(cr, version):
|
|
cr.execute("""
|
|
ALTER TABLE fp_part_catalog DROP COLUMN IF EXISTS revision_number;
|
|
""")
|