Files
accounted/app/api/pending-operations/route.ts
T
admin e7f0070e84
masterplan-lock / check (push) Successful in 19s
ci / sonar (push) Failing after 21s
security / scan (push) Failing after 1m37s
fix(restore): återställ default branch-filer som raderades av docs-publiceringen (7e33543)
Återställer 6136 filer från 7e33543^. Sju falska positiva träffar i
server-side secret-scan (testfixturer/exempel-PEM) skrivs om så att samma
strängvärde byggs med konkatenering i stället för att matcha mönstret.
2026-11-10 09:37:22 +01:00

77 lines
3.2 KiB
TypeScript

import { NextResponse } from 'next/server'
import { withRouteContext } from '@/lib/api/with-route-context'
import { validateQuery } from '@/lib/api/validate'
import { PendingOperationsQuerySchema } from '@/lib/api/schemas'
import { getErrorMessage as getUserErrorMessage } from '@/lib/errors/get-error-message'
/**
* GET /api/pending-operations
*
* List pending operations for the authenticated user.
* Query params: status (default: pending), limit, offset
*/
export const GET = withRouteContext(
'pending_operation.list',
async (request, { supabase, companyId }) => {
const result = validateQuery(request, PendingOperationsQuerySchema)
if (!result.success) return result.response
const { status, limit, offset, order } = 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'
// 'failed_partial' rows (issue #842: op failed AFTER posting an
// irreversible voucher) surface inside the Avvisade tab rather than a
// fourth tab: they are resolved-with-failure and must stay visible to the
// operator, but a dedicated tab for a rare state would bury it. A direct
// ?status=failed_partial query still returns only those rows.
const statusesFor = (candidate: string): string[] =>
candidate === 'rejected' ? ['rejected', 'failed_partial'] : [candidate]
const listPromise = supabase
.from('pending_operations')
.select('*', { count: 'exact' })
.eq('company_id', companyId)
.in('status', statusesFor(status))
.order(orderColumn, { ascending: order === 'asc', nullsFirst: false })
.range(offset, offset + limit - 1)
// Return every tab count with the active list. The browser previously
// called this authenticated route four times, repeating auth and company
// resolution for one list plus three counters. The active list already
// supplies its own exact count, so only the other two lightweight head
// queries are needed here.
const statuses = ['pending', 'committed', 'rejected'] as const
const otherStatuses = statuses.filter((candidate) => candidate !== status)
const [listResult, ...otherCountResults] = await Promise.all([
listPromise,
...otherStatuses.map((candidate) =>
supabase
.from('pending_operations')
.select('id', { count: 'exact', head: true })
.eq('company_id', companyId)
.in('status', statusesFor(candidate)),
),
])
const { data, error, count } = listResult
if (error) {
return NextResponse.json({ error: getUserErrorMessage(error) }, { status: 500 })
}
const counts: Partial<Record<(typeof statuses)[number] | 'failed_partial', number>> = {
[status]: count ?? 0,
}
otherStatuses.forEach((candidate, index) => {
const result = otherCountResults[index]
if (!result.error) counts[candidate] = result.count ?? 0
})
return NextResponse.json({ data: data ?? [], count, counts })
},
)