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

14
fusion_plating/fusion_plating_culture/security/fp_culture_security.xml
View File

@@ -8,37 +8,37 @@
<!-- ================================================================== -->
<!-- The Culture module reuses the core Fusion Plating groups: -->
<!-- group_fusion_plating_operator — read values and rotations -->
<!-- group_fusion_plating_supervisor — create recognitions -->
<!-- group_fusion_plating_manager — full CRUD on sets and values -->
<!-- group_fusion_plating_operator - read values and rotations -->
<!-- group_fusion_plating_supervisor - create recognitions -->
<!-- group_fusion_plating_manager - full CRUD on sets and values -->
<!-- No new groups are introduced here. ACLs live in -->
<!-- security/ir.model.access.csv. Record rules for multi-company -->
<!-- isolation live below. -->
<!-- ================================================================== -->
<record id="fp_value_set_company_rule" model="ir.rule">
<field name="name">Fusion Plating: Value Set — multi-company</field>
<field name="name">Fusion Plating: Value Set - multi-company</field>
<field name="model_id" ref="model_fusion_plating_value_set"/>
<field name="global" eval="True"/>
<field name="domain_force">['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]</field>
</record>
<record id="fp_value_company_rule" model="ir.rule">
<field name="name">Fusion Plating: Value — multi-company</field>
<field name="name">Fusion Plating: Value - multi-company</field>
<field name="model_id" ref="model_fusion_plating_value"/>
<field name="global" eval="True"/>
<field name="domain_force">['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]</field>
</record>
<record id="fp_value_rotation_company_rule" model="ir.rule">
<field name="name">Fusion Plating: Value Rotation — multi-company</field>
<field name="name">Fusion Plating: Value Rotation - multi-company</field>
<field name="model_id" ref="model_fusion_plating_value_rotation"/>
<field name="global" eval="True"/>
<field name="domain_force">['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]</field>
</record>
<record id="fp_value_recognition_company_rule" model="ir.rule">
<field name="name">Fusion Plating: Recognition — multi-company</field>
<field name="name">Fusion Plating: Recognition - multi-company</field>
<field name="model_id" ref="model_fusion_plating_value_recognition"/>
<field name="global" eval="True"/>
<field name="domain_force">['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]</field>