Mattsson
32d9978f1b
* 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>
37 lines
2.1 KiB
SQL
37 lines
2.1 KiB
SQL
-- Migration: K3 component depreciation (komponentavskrivning)
|
|
--
|
|
-- BFNAR 2012:1 ch.17.4 requires K3-reporting entities to apply the
|
|
-- "component approach" to substantial fixed assets (real estate is the
|
|
-- canonical case): when significant components of an asset have materially
|
|
-- different useful lives, each component must be depreciated separately
|
|
-- on its own life. K2 (BFNAR 2016:10) has no such requirement and treats
|
|
-- the asset as a single unit.
|
|
--
|
|
-- The `k3_components` JSONB column was already added by the original
|
|
-- assets migration (20260516120000_assets_and_depreciation.sql) as a
|
|
-- reserved placeholder. This migration now activates the column by
|
|
-- documenting the shape via COMMENT and signalling the engine support.
|
|
-- The structural shape stays:
|
|
-- [{ name: string, cost: number, useful_life_months: number,
|
|
-- salvage_value?: number }]
|
|
--
|
|
-- Validation rules (enforced application-side via Zod, not DB CHECK,
|
|
-- because validating sum(cost) == acquisition_cost involves cross-column
|
|
-- math that PostgreSQL CHECKs cannot express on JSONB):
|
|
-- - sum of component costs equals acquisition_cost (±1 kr tolerance)
|
|
-- - every component has cost > 0 and useful_life_months > 0
|
|
-- - salvage_value (if present) ≤ component cost
|
|
-- - array must be non-empty when set to non-null
|
|
--
|
|
-- Only meaningful for companies with accounting_framework = 'k3' (added in
|
|
-- 20260526121500_k3_framework.sql). The API layer rejects k3_components
|
|
-- writes for K2 companies with K3_REQUIRED_FOR_COMPONENTS.
|
|
--
|
|
-- No schema change is needed beyond refreshing the column comment — the
|
|
-- column itself already exists with type JSONB.
|
|
|
|
COMMENT ON COLUMN public.assets.k3_components IS
|
|
'K3 BFNAR 2012:1 ch 17.4 components. When non-null, asset is depreciated per-component instead of by depreciation_method. Shape: [{ name: string, cost: number, useful_life_months: number, salvage_value?: number }]. Only meaningful for companies with accounting_framework=k3. Sum of component costs must equal acquisition_cost; enforced in application code (Zod) because the cross-column constraint cannot be expressed in a CHECK on JSONB.';
|
|
|
|
NOTIFY pgrst, 'reload schema';
|