Files
accounted/lib/bokslut/__tests__/rounding.test.ts
T
MattssonandClaude Opus 4.7 32d9978f1b Fix/chrome pdf preview csp (#572)
* feat: add option to exclude year-end closing entries in SIE export and related reports

* delete docs

* fix: allow Chrome's PDF viewer in verifikat document preview

The /api/documents/:id/inline route shipped with
`object-src 'none'` in its CSP, which blocked Chrome's built-in PDF
viewer (it renders inline PDFs via an internal <embed>). Users on
Chrome saw "Det här innehållet har blockerats" when expanding a PDF
attachment in the bookkeeping view; Firefox (PDF.js) and Edge (own
viewer) were unaffected, and JPGs worked because <img> isn't subject
to object-src.

Drops the CSP for this route to the minimum needed for embeddability:
`frame-ancestors 'self'`. X-Content-Type-Options: nosniff plus the
fixed Content-Type from the handler already block MIME confusion;
X-Frame-Options: SAMEORIGIN + frame-ancestors still block clickjacking.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(auth): add webmail deep link to email confirmation screens

Mirrors Stripe's signup UX: after asking the user to verify their email,
detect their webmail provider from the domain and show a button that
opens the inbox in a new tab. Gmail gets a from:<sender> search
pre-populated; Outlook/Yahoo/iCloud/Proton open the inbox directly.
Unknown / custom domains fall back to the existing copy.

Sender address is configurable via NEXT_PUBLIC_BRANDING_AUTH_EMAIL_FROM
(default noreply@gnubok.se) so white-label installs can match their
Supabase Auth SMTP config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(auth): unblock first-time password set for BankID users with MFA

Supabase rejects updateUser({password}) and mfa.unenroll with "AAL2 session
is required" whenever a TOTP factor is enrolled. BankID magic-link logins
produce AAL1, and middleware skips MFA enforcement for bankid_linked users,
so they had no path to AAL2 — leaving them unable to set a backup password
or disable MFA without going through the email-recovery escape hatch.

- /api/account/password: branch on app_metadata.has_password. First-time set
  writes via service.auth.admin.updateUserById (no existing credential to
  protect, AAL2 guard does not apply). Change-password keeps the user-session
  updateUser so AAL2 still fires for credential rotation.
- /mfa/verify: accept a safeReturnTo query param and route there after
  successful verify, so step-up flows can land back where they came from.
- SecuritySettings: detect the AAL2 error from both change-password and
  mfa.unenroll and redirect through /mfa/verify?returnTo=/settings/account
  instead of toasting a dead-end error.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Add tests and rounding utility for öre precision in bokslut calculations

- Implemented `roundOre` function for rounding SEK amounts to two decimal places, ensuring consistent monetary calculations.
- Introduced `ORE_TOLERANCE` constant for comparing rounded amounts, facilitating invariant checks in financial entries.
- Created comprehensive tests for `roundOre`, covering typical cases, edge cases, and idempotency.
- Added year-end invariants tests to verify database-level guarantees for closing entries, ensuring they balance to the öre and reject discrepancies.
- Developed end-to-end tests for the dispositions chain, validating the correctness of calculations across various scenarios.

* fix: update PDF rendering to remove Swish QR code generation and set default to disable Swish visibility

* fix: enhance security by rejecting data URIs in safeReturnTo function tests

* fix: improve rounding logic in roundOre function and add customer_type migration

* fix: add customer_type column to customers and enforce CHECK constraint

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-26 22:29:41 +02:00

66 lines
2.2 KiB
TypeScript

import { describe, it, expect } from 'vitest'
import { roundOre, ORE_TOLERANCE } from '../rounding'
describe('roundOre', () => {
it('rounds typical positive amounts to two decimals', () => {
expect(roundOre(1.234)).toBe(1.23)
expect(roundOre(1.235)).toBe(1.24)
expect(roundOre(1.236)).toBe(1.24)
})
it('rounds negative amounts symmetrically', () => {
// Math.round rounds half toward +∞: -1.235 -> -1.23.
// Verified behavior so callers can rely on it.
expect(roundOre(-1.234)).toBe(-1.23)
expect(roundOre(-1.236)).toBe(-1.24)
})
it('returns 0 unchanged', () => {
expect(roundOre(0)).toBe(0)
// Math.round(-0 * 100) preserves the negative-zero sign; treat it as
// numerically equal to 0 rather than enforcing Object.is equality.
expect(roundOre(-0)).toEqual(-0)
expect(Math.abs(roundOre(-0))).toBe(0)
})
it('exposes a half-öre tolerance constant', () => {
expect(ORE_TOLERANCE).toBe(0.005)
})
it('sum of rounded parts equals rounded sum for representative cases', () => {
const cases: number[][] = [
[100, 200, 300],
[1.11, 2.22, 3.33],
[1.005, 2.005, 3.005],
[-100, 50, 50],
[-1.234, 2.345, -3.456],
[0.1, 0.2, 0.3], // classic IEEE 754 trap
[12345.67, -12345.67],
[1_000_000.01, 2_000_000.02, 3_000_000.03],
]
// Half-up rounding doesn't preserve sums exactly: each part can shift
// by up to half an öre, so cumulative drift over N parts is bounded by
// N * ORE_TOLERANCE. The pathological case is [1.005, 2.005, 3.005] —
// three exact-half values that all round up to .01, drifting the sum
// by one öre versus summing then rounding.
for (const parts of cases) {
const summedThenRounded = roundOre(parts.reduce((a, b) => a + b, 0))
const roundedThenSummed = roundOre(
parts.map(roundOre).reduce((a, b) => a + b, 0)
)
expect(
Math.abs(summedThenRounded - roundedThenSummed),
`parts=${JSON.stringify(parts)}`
).toBeLessThanOrEqual(ORE_TOLERANCE * parts.length)
}
})
it('roundOre is idempotent', () => {
const samples = [1.005, -2.345, 99.999, -0.005]
for (const s of samples) {
expect(roundOre(roundOre(s))).toBe(roundOre(s))
}
})
})