letsbe/pn-new-crm
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore(copy): em-dash sweep across user-facing JSX text + bump lint to error

Browse Source 
Replaced 174 em-dashes (—) with " - " (space-hyphen-space) across 49
files in src/components + src/app. The em-dash reads as a tell-tale
"AI-generated" marker per the user's design feedback; hyphens with
spaces preserve the connector semantics without the AI tint.

Touched only lines outside pure-comment context (// /* * */). Code
comments, JSDoc, audit-log strings, structured logging strings, and
templates outside the lint scope retain their em-dashes for now —
they're not user-visible.

Also captured two remaining cases that used the `—` HTML entity
instead of the literal character (system-monitoring-dashboard,
interest-stage-picker) — replaced with a plain hyphen.

Bumped the existing `no-restricted-syntax` rule from `warn` → `error`
in eslint.config.mjs scoped to src/components/**/*.tsx +
src/app/**/*.tsx. New code reintroducing em-dashes in JSX text now
fails the lint gate.

Verified: tsc clean, vitest 1448/1448, eslint 0 em-dash warnings.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt
2026-05-21 20:02:58 +02:00
parent 292a8b5e4a
commit f0dbefcac2
59 changed files with 213 additions and 205 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/app/docs/deal-pulse/page.tsx
View File

@@ -1,7 +1,7 @@
import type { Metadata } from 'next';
export const metadata: Metadata = {
title: 'Deal Pulse & Heat — Port Nimara CRM',
title: 'Deal Pulse & Heat - Port Nimara CRM',
description:
'How the deal pulse chip + heat score work: signals, calibration, and what to do when a deal goes cold.',
};
@@ -35,7 +35,7 @@ export default function DealPulseDocsPage() {
<p>
The colored chip on each interest is a fast read of{' '}
<strong>how hot the deal is right now</strong> based on what&apos;s been happening on it
lately — not a prediction, not an AI score, just a mechanical rollup of recent activity.
lately - not a prediction, not an AI score, just a mechanical rollup of recent activity.
</p>
</section>
@@ -53,7 +53,7 @@ export default function DealPulseDocsPage() {
<dt className="font-semibold text-amber-900">Warm</dt>
<dd className="text-amber-900/90">
Activity in the last 14–30 days. The deal isn&apos;t neglected but the cadence has
slowed — usually means a follow-up reminder is the right next action.
slowed - usually means a follow-up reminder is the right next action.
</dd>
</div>
<div className="rounded-md border bg-slate-100 p-3">
@@ -86,7 +86,7 @@ export default function DealPulseDocsPage() {
</li>
<li>
<strong>Time at current stage.</strong> Stagnation drags the score down even if other
signals look good — a deal stuck at Reservation for six weeks should not read hot.
signals look good - a deal stuck at Reservation for six weeks should not read hot.
</li>
</ul>
<p className="text-muted-foreground">
@@ -128,7 +128,7 @@ export default function DealPulseDocsPage() {
Can I override the chip on a specific deal?
</summary>
<p className="mt-2 text-muted-foreground">
Not directly — the chip is a read-only summary. To change it, change the inputs: log a
Not directly - the chip is a read-only summary. To change it, change the inputs: log a
contact, advance a stage, or close the deal.
</p>
</details>