chore(plating): de-dash shipped code + intake-neutral customer emails
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:
@@ -15,7 +15,7 @@ class FpValue(models.Model):
|
||||
icon for display in kanban tiles.
|
||||
"""
|
||||
_name = 'fusion.plating.value'
|
||||
_description = 'Fusion Plating — Value'
|
||||
_description = 'Fusion Plating - Value'
|
||||
_order = 'set_id, sequence, number, name'
|
||||
|
||||
name = fields.Char(
|
||||
@@ -94,7 +94,7 @@ class FpValue(models.Model):
|
||||
result = []
|
||||
for rec in self:
|
||||
if rec.number:
|
||||
result.append((rec.id, f'#{rec.number} — {rec.name}'))
|
||||
result.append((rec.id, f'#{rec.number} - {rec.name}'))
|
||||
else:
|
||||
result.append((rec.id, rec.name))
|
||||
return result
|
||||
|
||||
@@ -17,7 +17,7 @@ class FpValueRecognition(models.Model):
|
||||
when they roll off a stand-up wall or a newsletter.
|
||||
"""
|
||||
_name = 'fusion.plating.value.recognition'
|
||||
_description = 'Fusion Plating — Value Recognition'
|
||||
_description = 'Fusion Plating - Value Recognition'
|
||||
_inherit = ['mail.thread', 'mail.activity.mixin']
|
||||
_order = 'nomination_date desc, id desc'
|
||||
|
||||
|
||||
@@ -13,12 +13,12 @@ class FpValueRotation(models.Model):
|
||||
|
||||
Used to drive "Fundamental of the Day/Week/Month" programs. The admin
|
||||
creates a rotation, picks a set and a period, and enables it. This
|
||||
module does NOT ship an ir.cron — the shop admin wires a cron to call
|
||||
module does NOT ship an ir.cron - the shop admin wires a cron to call
|
||||
`_cron_advance_rotation` if they want automatic advancement. Many
|
||||
shops prefer to advance the rotation manually at a weekly stand-up.
|
||||
"""
|
||||
_name = 'fusion.plating.value.rotation'
|
||||
_description = 'Fusion Plating — Value Rotation Schedule'
|
||||
_description = 'Fusion Plating - Value Rotation Schedule'
|
||||
_inherit = ['mail.thread']
|
||||
_order = 'name'
|
||||
|
||||
@@ -133,7 +133,7 @@ class FpValueRotation(models.Model):
|
||||
"""Cron entry point.
|
||||
|
||||
A shop admin can wire an ir.cron to this method. The module
|
||||
intentionally does not ship one — different shops want different
|
||||
intentionally does not ship one - different shops want different
|
||||
cadences. Only advances rotations whose next_rotation_date is
|
||||
today or earlier.
|
||||
"""
|
||||
|
||||
@@ -14,10 +14,10 @@ class FpValueSet(models.Model):
|
||||
may have several sets (historical, draft, archived) but usually only
|
||||
one is marked primary.
|
||||
|
||||
The module ships NO seed data — this is a generic framework.
|
||||
The module ships NO seed data - this is a generic framework.
|
||||
"""
|
||||
_name = 'fusion.plating.value.set'
|
||||
_description = 'Fusion Plating — Value Set'
|
||||
_description = 'Fusion Plating - Value Set'
|
||||
_inherit = ['mail.thread', 'mail.activity.mixin']
|
||||
_order = 'is_primary desc, name'
|
||||
|
||||
|
||||
Reference in New Issue
Block a user