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>
52 lines
2.1 KiB
TypeScript
52 lines
2.1 KiB
TypeScript
/**
|
|
* READ-ONLY: inspect the actual schema of public.skatteverket_tokens in prod.
|
|
* Confirms whether the UNIQUE(user_id) constraint exists and under what name.
|
|
*/
|
|
|
|
import { createClient } from '@supabase/supabase-js'
|
|
import { config } from 'dotenv'
|
|
import { resolve } from 'node:path'
|
|
|
|
config({ path: resolve(process.cwd(), '.env.local') })
|
|
|
|
const supabase = createClient(
|
|
process.env.NEXT_PUBLIC_SUPABASE_URL!,
|
|
process.env.SUPABASE_SERVICE_ROLE_KEY!,
|
|
{ auth: { persistSession: false } },
|
|
)
|
|
|
|
async function main() {
|
|
// Try a row-count query to see if the table exists at all
|
|
const { count, error: countErr } = await supabase
|
|
.from('skatteverket_tokens')
|
|
.select('*', { count: 'exact', head: true })
|
|
console.log('Table reachable:', !countErr, 'row count:', count, 'error:', countErr?.message ?? 'none')
|
|
|
|
// Use the postgrest schema endpoint to introspect via the OpenAPI spec
|
|
const { data: openapiResp, error: openapiErr } = await supabase
|
|
.from('skatteverket_tokens')
|
|
.select('id, user_id, expires_at, refresh_count, scope')
|
|
.limit(1)
|
|
console.log('Sample select error:', openapiErr?.message ?? 'none', ', rows:', openapiResp?.length ?? 0)
|
|
|
|
// Fetch from pg_constraint via a dedicated RPC if available, else via raw query
|
|
// Supabase JS doesn't expose raw SQL, so we use a workaround: try to provoke
|
|
// the constraint name from the upsert error itself with a dummy row.
|
|
console.log('\nProbing existing rows to count duplicates per user_id…')
|
|
const { data: rows, error: rowsErr } = await supabase
|
|
.from('skatteverket_tokens')
|
|
.select('id, user_id, created_at')
|
|
.order('created_at', { ascending: false })
|
|
if (rowsErr) {
|
|
console.error('rows fetch failed:', rowsErr.message)
|
|
return
|
|
}
|
|
const byUser = new Map<string, number>()
|
|
for (const r of rows ?? []) byUser.set(r.user_id, (byUser.get(r.user_id) ?? 0) + 1)
|
|
console.log(` ${rows?.length ?? 0} total rows across ${byUser.size} distinct user_ids`)
|
|
const dupes = [...byUser.entries()].filter(([, n]) => n > 1)
|
|
if (dupes.length) console.log(' duplicates:', dupes)
|
|
}
|
|
|
|
main().catch(err => { console.error(err); process.exit(1) })
|