Files
accounted/app/api/agent/conversations/route.ts
T
Jakob WennbergandClaude Sonnet 5 ec27228a8e style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890)
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>
2026-07-04 15:58:06 +02:00

61 lines
2.5 KiB
TypeScript

import { createClient } from '@/lib/supabase/server'
import { NextResponse } from 'next/server'
import { getActiveCompanyId } from '@/lib/company/context'
// GET /api/agent/conversations
//
// Query params:
// archived: 'true' | 'false' (default 'false')
// pinned: 'true' filters to pinned only
// intent: 'general.help' (or any intent id), filter
// q: case-insensitive substring match on title/context_ref
// limit: 1..200, default 50
//
// Returns: { data: [{ id, intent_id, context_ref, title, pinned, archived,
// last_message_at, created_at }] }
//
// Ordered: pinned first (within archived bucket), then last_message_at desc.
// Used by the /chat sidebar and "resume conversation" UI in the sheet.
export async function GET(request: Request) {
const supabase = await createClient()
const { data: { user } } = await supabase.auth.getUser()
if (!user) return NextResponse.json({ error: 'Unauthorized' }, { status: 401 })
const companyId = await getActiveCompanyId(supabase, user.id)
if (!companyId) return NextResponse.json({ error: 'No active company' }, { status: 400 })
const url = new URL(request.url)
const archived = url.searchParams.get('archived') === 'true'
const pinnedOnly = url.searchParams.get('pinned') === 'true'
const intent = url.searchParams.get('intent') ?? null
const q = url.searchParams.get('q')?.trim() ?? ''
const limit = Math.min(Math.max(Number(url.searchParams.get('limit')) || 50, 1), 200)
let query = supabase
.from('agent_conversations')
.select(
'id, intent_id, context_ref, title, pinned, archived, last_message_at, last_message_preview, created_at',
)
.eq('company_id', companyId)
.eq('archived', archived)
if (pinnedOnly) query = query.eq('pinned', true)
if (intent) query = query.eq('intent_id', intent)
if (q.length > 0) {
// Pattern is sanitized via Postgres' percent-handling; ilike accepts the
// % wildcard and we only inject the user's substring between them.
const safe = q.replace(/[%_]/g, (m) => `\\${m}`)
query = query.or(`title.ilike.%${safe}%,context_ref.ilike.%${safe}%`)
}
// Sort: pinned first, then most recent message.
query = query
.order('pinned', { ascending: false })
.order('last_message_at', { ascending: false, nullsFirst: false })
.limit(limit)
const { data, error } = await query
if (error) return NextResponse.json({ error: error.message }, { status: 500 })
return NextResponse.json({ data: data ?? [] })
}