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

22
fusion_plating/fusion_plating_process_chrome/__manifest__.py
View File

@@ -4,27 +4,27 @@
# Part of the Fusion Plating product family.
{
'name': 'Fusion Plating — Chrome Plating Process Pack',
'name': 'Fusion Plating - Chrome Plating Process Pack',
'version': '19.0.1.0.0',
'category': 'Manufacturing/Plating',
'summary': 'Chrome plating process types — hard and decorative, hexavalent and trivalent — with bath parameter schemas and carcinogen hazard awareness.',
'summary': 'Chrome plating process types - hard and decorative, hexavalent and trivalent - with bath parameter schemas and carcinogen hazard awareness.',
'description': """
Fusion Plating — Chrome Plating Process Pack
Fusion Plating - Chrome Plating Process Pack
==============================================
Part of the Fusion Plating product family by Nexa Systems Inc.
This data-only module plugs into the ``fusion_plating`` core and seeds the
process taxonomy and bath chemistry schemas specific to chrome (chromium)
plating. No new models, no new views — just records loaded with
plating. No new models, no new views - just records loaded with
``noupdate="1"`` so downstream customizations survive upgrades.
Process types shipped
---------------------
* Hard Chrome — Hexavalent (Cr(VI))
* Decorative Chrome — Hexavalent (Cr(VI))
* Hard Chrome — Trivalent (Cr(III))
* Decorative Chrome — Trivalent (Cr(III))
* Hard Chrome - Hexavalent (Cr(VI))
* Decorative Chrome - Hexavalent (Cr(VI))
* Hard Chrome - Trivalent (Cr(III))
* Decorative Chrome - Trivalent (Cr(III))
* Chrome Strike
Bath parameters shipped
@@ -42,14 +42,14 @@ hex-chrome process type carries ``hazard_notes`` that flag:
* Ontario Reg. 833 ceiling exposure limit 0.05 mg/m³ as Cr(VI).
* Mandatory mist suppression and medical surveillance.
* Toronto Ch. 681 sewer limits — Cr(VI) 2 mg/L, total Cr 4 mg/L.
* Toronto Ch. 681 sewer limits - Cr(VI) 2 mg/L, total Cr 4 mg/L.
* NPRI Part 1B reporting, CEPA Schedule 1 listing.
* Mandatory rinse-water segregation — no storm sewer discharge
* Mandatory rinse-water segregation - no storm sewer discharge
(storm limit 0.0008 mg/L Cr(VI)).
* Industry transition to trivalent chrome where part specs allow.
Trivalent (Cr(III)) variants are flagged as the preferred choice for new
installations, with reduced toxicity and lower fume generation — but
installations, with reduced toxicity and lower fume generation - but
still subject to Toronto total-chromium discharge limits.
Install this module after ``fusion_plating``. It depends only on the core