admin/Odoo-Modules
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(plating): de-dash shipped code + intake-neutral customer emails

Browse Source 
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>
This commit is contained in:
gsinghpal
2026-06-05 00:16:19 -04:00
parent c9eb61ee0c
commit 8c76a16366
789 changed files with 4692 additions and 4692 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
fusion_plating/fusion_plating_certificates/views/fp_certificate_views.xml
View File

@@ -39,13 +39,13 @@
<field name="arch" type="xml">
<form>
<header>
<!-- Phase D5 — Nadcap-cert restriction enforced at MODEL
<!-- Phase D5 - Nadcap-cert restriction enforced at MODEL
layer via ir.rule (rule_fp_certificate_nadcap_qm_only
in fp_cert_security.xml). Single Issue button visible
to all Manager+ when state=draft. Manager clicking
Issue on a Nadcap cert gets AccessError from the rule.
(Strategy B with user_has_groups() inside invisible=
was rejected by Odoo 19 view validator — see CLAUDE.md
was rejected by Odoo 19 view validator - see CLAUDE.md
rule 13f.) -->
<button name="action_issue" string="Issue"
type="object" class="btn-primary"
@@ -91,7 +91,7 @@
<field name="name" readonly="1"/>
</h1>
</div>
<!-- Main info — collapsed from 3 separate groups
<!-- Main info - collapsed from 3 separate groups
into 1 to eliminate the dead rows that
appeared when one sub-group ran shorter than
the other. Left column is identity / signer /
@@ -125,11 +125,11 @@
<field name="mean_nip_mils" readonly="1"/>
</group>
</group>
<!-- SPC rebalanced — spec/min/max on the left,
<!-- SPC rebalanced - spec/min/max on the left,
derived stats on the right; trend_explanation
spans both columns so the long message doesn't
get cropped. -->
<group string="SPC — Statistical Process Control">
<group string="SPC - Statistical Process Control">
<group>
<field name="spec_min_mils"/>
<field name="spec_max_mils"/>
@@ -169,7 +169,7 @@
</page>
<page string="Certificate PDF" name="pdf">
<!-- Manual-attach banner for orphan cert types
(Nadcap / Mill Test / Customer-Specific) —
(Nadcap / Mill Test / Customer-Specific) -
spec 2026-05-27. action_issue refuses to
finalize these types without a PDF. -->
<div class="alert alert-warning" role="alert"

2
fusion_plating/fusion_plating_certificates/views/fp_certificates_menu.xml
View File

@@ -16,7 +16,7 @@
<field name="domain">[('certificate_type', '=', 'thickness_report')]</field>
</record>
<!-- Phase 1 — re-parented under Plating → Quality. Certificates are
<!-- Phase 1 - re-parented under Plating → Quality. Certificates are
a quality output, not a separate top-level concern. -->
<menuitem id="menu_fp_certificates"
name="Certificates"

2
fusion_plating/fusion_plating_certificates/views/res_partner_views.xml
View File

@@ -71,7 +71,7 @@
</field>
</record>
<!-- Sub 6 — Per-contact routing flags on the contact's own form
<!-- Sub 6 - Per-contact routing flags on the contact's own form
(opens when editing a child contact row). Applied to every
res.partner form so delivery-location partners and their child
contacts both surface the same flags. -->