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

2
fusion_plating/fusion_plating_quality/reports/fp_contract_review_report.xml
View File

@@ -3,7 +3,7 @@
Copyright 2026 Nexa Systems Inc.
License OPL-1 (Odoo Proprietary License v1.0)
Part of the Fusion Plating product family.
Sub 4 — Contract Review QWeb report action.
Sub 4 - Contract Review QWeb report action.
-->
<odoo>

6
fusion_plating/fusion_plating_quality/reports/fp_contract_review_template.xml
View File

@@ -3,7 +3,7 @@
Copyright 2026 Nexa Systems Inc.
License OPL-1 (Odoo Proprietary License v1.0)
Part of the Fusion Plating product family.
Sub 4 — Contract Review QA-005 QWeb template (1:1 paper form).
Sub 4 - Contract Review QA-005 QWeb template (1:1 paper form).
-->
<odoo>
@@ -80,7 +80,7 @@
<td><span t-field="doc.date_received"/></td>
<td><b>Qty</b></td>
<td><span t-field="doc.qty"/>
— Due <span t-field="doc.due_date"/></td>
- Due <span t-field="doc.due_date"/></td>
</tr>
</table>
@@ -225,7 +225,7 @@
<tr><td>1</td><td>Not Likely</td><td>Current approach / process will effectively avoid this risk</td></tr>
<tr><td>2</td><td>Low Likelihood</td><td>Current approach / process has usually mitigated</td></tr>
<tr><td>3</td><td>Likely</td><td>Current approach / process may mitigate this risk</td></tr>
<tr><td>4</td><td>Highly Likely</td><td>Current approach / process cannot mitigate — different approach might</td></tr>
<tr><td>4</td><td>Highly Likely</td><td>Current approach / process cannot mitigate - different approach might</td></tr>
<tr><td>5</td><td>Near Certainty</td><td>Current approach / process cannot mitigate the risk and no processes are available</td></tr>
</table>
</div>