Jakob WennbergandClaude Sonnet 5
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>
46 lines
1.7 KiB
TypeScript
46 lines
1.7 KiB
TypeScript
import { createClient } from '@/lib/supabase/server'
|
|
import { NextResponse } from 'next/server'
|
|
import { validateQuery } from '@/lib/api/validate'
|
|
import { PendingOperationsQuerySchema } from '@/lib/api/schemas'
|
|
import { requireCompanyId } from '@/lib/company/context'
|
|
|
|
/**
|
|
* GET /api/pending-operations
|
|
*
|
|
* List pending operations for the authenticated user.
|
|
* Query params: status (default: pending), limit, offset
|
|
*/
|
|
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 requireCompanyId(supabase, user.id)
|
|
|
|
const result = validateQuery(request, PendingOperationsQuerySchema)
|
|
if (!result.success) return result.response
|
|
const { status, limit, offset } = result.data
|
|
|
|
// Terminal tabs (Godkända/Avvisade) order by when the op was RESOLVED, not
|
|
// created: auto-expired ops are ≥30 days old by construction, so a
|
|
// created_at ordering would bury a fresh expiry sweep below a month of
|
|
// newer rejections and the "Utgick automatiskt" context would never be seen.
|
|
const orderColumn = status === 'pending' ? 'created_at' : 'resolved_at'
|
|
|
|
const { data, error, count } = await supabase
|
|
.from('pending_operations')
|
|
.select('*', { count: 'exact' })
|
|
.eq('company_id', companyId)
|
|
.eq('status', status)
|
|
.order(orderColumn, { ascending: false, nullsFirst: false })
|
|
.range(offset, offset + limit - 1)
|
|
|
|
if (error) {
|
|
return NextResponse.json({ error: error.message }, { status: 500 })
|
|
}
|
|
|
|
return NextResponse.json({ data: data ?? [], count })
|
|
}
|