Files
accounted/lib/sales-orders/transitions.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

74 lines
3.1 KiB
TypeScript

import type { SupabaseClient } from '@supabase/supabase-js'
import type { SalesOrder, SalesOrderStatus } from '@/types'
import { loadSalesOrder } from './load'
import { hasOpenInvoices } from './write'
import { fail, failDb, type ServiceResult } from './result'
export type SalesOrderTransition = 'confirm' | 'cancel' | 'reopen'
/**
* Header state machine. `completed` is never set here: it is maintained by
* the DB (refresh_sales_order_completion) from the derived invoiced
* quantities, and flips back to `confirmed` when a linked invoice is
* cancelled or credited.
*
* draft -confirm-> confirmed
* draft -cancel--> cancelled
* confirmed -cancel--> cancelled (refused while linked invoices exist)
* cancelled -reopen--> draft (refused while linked invoices exist)
*/
const ALLOWED: Record<SalesOrderTransition, { from: SalesOrderStatus[]; to: SalesOrderStatus }> = {
confirm: { from: ['draft'], to: 'confirmed' },
cancel: { from: ['draft', 'confirmed'], to: 'cancelled' },
reopen: { from: ['cancelled'], to: 'draft' },
}
export async function transitionSalesOrder(
supabase: SupabaseClient,
params: { companyId: string; orderId: string; action: SalesOrderTransition },
): Promise<ServiceResult<{ order: SalesOrder }>> {
const { companyId, orderId, action } = params
const current = await loadSalesOrder(supabase, companyId, orderId)
if (!current.ok) return current
const order = current.order
const rule = ALLOWED[action]
if (!rule.from.includes(order.status)) {
return fail('SALES_ORDER_INVALID_STATE', { status: order.status, action })
}
if (action === 'cancel' || action === 'reopen') {
const open = await hasOpenInvoices(supabase, companyId, orderId)
if (!open.ok) return failDb(open.dbError)
if (open.open) return fail('SALES_ORDER_HAS_INVOICES')
}
if (action === 'confirm' && !order.customer_id) return fail('SALES_ORDER_CUSTOMER_MISSING')
const now = new Date().toISOString()
// Compare-and-set on the status read above so two concurrent transitions
// cannot both win. Object literal on purpose (schema guard): undefined
// keys are dropped by JSON serialisation, null keys clear the column.
const { data: updated, error } = await supabase
.from('sales_orders')
.update({
status: rule.to,
confirmed_at: action === 'confirm' ? now : action === 'reopen' ? null : undefined,
cancelled_at: action === 'cancel' ? now : action === 'reopen' ? null : undefined,
completed_at: action === 'reopen' ? null : undefined,
})
.eq('id', orderId)
.eq('company_id', companyId)
.eq('status', order.status)
.select('id')
if (error) return failDb(error)
if (!updated || updated.length === 0) return fail('SALES_ORDER_INVALID_STATE', { status: order.status, action })
if (action === 'confirm') {
// Hand-linked invoice lines may already cover the order: let the DB
// evaluate completion right away instead of waiting for the next line
// change. Best effort; the triggers keep it honest afterwards.
await supabase.rpc('refresh_sales_order_completion', { p_order_id: orderId })
}
return loadSalesOrder(supabase, companyId, orderId)
}