Jakob Wennberg
ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
24 lines
930 B
TypeScript
24 lines
930 B
TypeScript
'use client'
|
|
|
|
import { useCompany } from '@/contexts/CompanyContext'
|
|
|
|
/**
|
|
* Returns whether the current user can perform write actions in the
|
|
* active company. Viewers (role === 'viewer') get `canWrite = false`;
|
|
* owner / admin / member all get `canWrite = true`. Users with no active
|
|
* company (null role) also get `canWrite = false`.
|
|
*
|
|
* Used by every write-action button (create / edit / delete / send /
|
|
* approve / etc.) across the dashboard to render the button in a
|
|
* disabled state with a lock icon and tooltip.
|
|
*
|
|
* This is the UI layer of the viewer role enforcement. The API layer
|
|
* (`requireWritePermission()`) and RLS layer (`current_user_can_write()`)
|
|
* remain the security-critical backstops: this hook only controls what
|
|
* the user sees and can click.
|
|
*/
|
|
export function useCanWrite(): { canWrite: boolean } {
|
|
const { role } = useCompany()
|
|
return { canWrite: role !== null && role !== 'viewer' }
|
|
}
|