d54b43f80f
* fix(invoices): anchor the PDF logo to the top-left of its header cell The logo box is always the full 240x80pt reserved area (any larger logo is clamped to exactly that), so objectFit: 'contain' placed the image inside it with the default 50% 50% centering. A wide banner logo fills the width and lands on the left margin, but a near-square logo scaled down to the 80pt height cap is only ~117pt wide and got pushed ~60pt in from the margin, which reads as a misaligned logo and forced companies to reshape their artwork. Anchor the image top-left so every aspect ratio starts at the margin. Covered by a test that renders the real PDF and reads the image placement matrix out of the content stream, for both a wide and a near-square logo. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * feat(invoices): show the real delivery outcome in the send history "Skickad" only meant the email provider accepted the message, so a bounced invoice looked identical to one that arrived. Resend reports the outcome asynchronously; that report now lands on the delivery row and drives the history: green is reserved for a confirmed delivery, bounce/blocked reads red, delayed and spam-marked read amber, and an accepted-but-unconfirmed send is neutral instead of falsely green. The report arrives on a signed webhook and may only touch the three new provider status columns of an already sent, unredacted row: the WORM trigger proves nothing else changed, and a lower ranked or older report can never downgrade an observed failure. The provider reason text can quote the failing address, so it is masked on read and cleared by the daily PII redaction job. Timestamps also formatted in Europe/Stockholm instead of falling back to the runtime zone, which rendered a 14:05 send as 12:05 on Vercel. Delivery reports are per message, never per recipient: Resend sends one event for the whole message, so splitting a send per recipient would be the only way to get finer granularity, at the cost of CC. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * feat(stripe): make the integration feed-only Stripe sync now only imports balance transactions into the transactions inbox, like any bank feed; nothing auto-books. The event/settlement sync (lib/sync.ts, lib/payouts.ts) stays in the repo but is no longer wired to any route or cron: the 15-min sync cron is removed from vercel.json. Payment links on invoice send are unchanged; their payments arrive as feed rows and are matched manually. - /sync runs only syncStripeBalanceTransactions; response is { success, transactions } - connecting via OAuth enables the nightly feed by default (toggle stays as opt-out) - panel: needs-review section and plumbing removed, copy rewritten to transactions-first (sv + en), toast reports fetched/imported/linked and calls out an empty result instead of silent all-zeros Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(api): return the article currency from the v1 article list The dashboard, importer, export and MCP article surfaces all learned to carry a non-SEK article price (#1166, #1183, #1184), but the v1 projection still omitted currency. An API or agent caller therefore read price_excl_vat with nothing marking it as EUR and would copy the number straight onto a SEK invoice line, at a nine-to-one error. Adds currency to the projection, the response shape and the example, plus a pitfall stating the price is not always SEK and that this endpoint does no FX conversion. Additive field only; no migration (articles.currency already exists). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * feat(settings): replace the settings modal with a routed panel sheet Settings now renders as a sheet that fills the main panel, sliding up over the page the user came from and back down on close, with the sidebar and frame left visible and usable. Behind it sits one shared master-detail surface: underline search across every section and subsection, the grouped section rail, and the active section as a direct-editing accordion. All 11 sections are decomposed into subsections, and the legacy *SettingsContent components compose the same pieces so the stacked and accordion layouts cannot drift. The sheet is the only presentation, on every entry path. The intercepting route handles in-app navigation and closes by popping the history entry, landing back on the page underneath. @settingsModal/default.tsx handles cold loads (refresh, deep link, new tab), where interception never fires; nothing is mounted underneath there, so it closes to the dashboard. Both branch on one shared predicate, isSheetSection, together with the settings layout, which must render nothing for those sections or the surface would stack twice behind the sheet and run every section's fetches twice. Closing is deliberate rather than incidental: the X, Esc, or navigating away. The dialog is non-modal so the sidebar's account popover and company switcher keep working with settings up, and an outside click no longer dismisses it. Sections land fully collapsed, and the scroll position of the page behind survives opening and closing the sheet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * feat: enhance article management and settings UI - Add PATCH test for toggling article active state without other fields. - Remove unused MessageCircle icon from DashboardContent. - Refactor AccountingFrameworkForm to use SettingsFieldRow for better help text display. - Update CompanyInfoForm, DimensionsToggle, and various settings forms to replace description with help text. - Remove redundant headings and intros in several settings components to streamline UI. - Improve help text for various settings in English and Swedish translations. - Update structured error messages for better clarity on article deletion. * refactor(ArticleDetailPage): remove unused imports and duplicate state variable * fix(settings): own deep-linked settings routes by route list, not nav visibility Review fixes from the settings panel sheet work: * isSheetSection reads the full settings route list so a hidden-but-deep-linked section (assistant before BankID, banking in sandbox, api without MCP) is claimed by the sheet instead of rendering the legacy shell around an empty panel * keep 503 on the Resend delivery webhook when the signing secret is unset, with a test pinning the behaviour * stripe callback route test coverage Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * refactor: update salary, tax, and templates settings components - Refactored SalarySettingsContent to use a form wrapper and improved payment settings UI. - Enhanced TaxSettingsContent with new signals for EU sales, KU obligations, and ROT/RUT deductions. - Updated TemplatesSettingsContent to remove legacy comments and improve readability. - Simplified navigation items by removing unnecessary constants and directly using hrefs. - Cleaned up translation files by removing deprecated keys and adding new descriptions for clarity. --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
106 lines
3.6 KiB
TypeScript
106 lines
3.6 KiB
TypeScript
'use client'
|
|
|
|
import { useCallback, useSyncExternalStore } from 'react'
|
|
import Link from 'next/link'
|
|
import { ExternalLink } from 'lucide-react'
|
|
import { Switch } from '@/components/ui/switch'
|
|
import {
|
|
SettingsRow,
|
|
SettingsRowEnd,
|
|
} from '@/components/settings/SettingsRows'
|
|
|
|
/**
|
|
* Per-user toggle for the periodisering wizard's auto-detection step.
|
|
*
|
|
* Backed by localStorage (key: `periodisering_autodetect_enabled`) because
|
|
* the company_settings table does not yet have a dedicated column for this
|
|
* preference, and the task description explicitly allows the persistence to
|
|
* be UI-local. A future migration can promote this to a real
|
|
* `company_settings.periodisering_autodetect_enabled boolean` column and
|
|
* the wizard's auto-detect step will read either source.
|
|
*
|
|
* Default: enabled. The wizard's auto-detect step renders regardless: the
|
|
* toggle merely controls whether the GET response includes `autoDetected`
|
|
* on subsequent fetches. (Today the API always returns it; the wizard step
|
|
* can early-out based on this setting locally.)
|
|
*/
|
|
const STORAGE_KEY = 'periodisering_autodetect_enabled'
|
|
|
|
function readStored(): boolean {
|
|
if (typeof window === 'undefined') return true
|
|
try {
|
|
const stored = window.localStorage.getItem(STORAGE_KEY)
|
|
return stored === null ? true : stored !== 'false'
|
|
} catch {
|
|
return true
|
|
}
|
|
}
|
|
|
|
/** Subscribe to localStorage changes from OTHER tabs. Same-tab updates are
|
|
* picked up via the explicit re-render after `setItem`: see
|
|
* `notifyChange` below. */
|
|
function subscribe(callback: () => void): () => void {
|
|
if (typeof window === 'undefined') return () => {}
|
|
const handler = (e: StorageEvent) => {
|
|
if (e.key === STORAGE_KEY || e.key === null) callback()
|
|
}
|
|
const customHandler = () => callback()
|
|
window.addEventListener('storage', handler)
|
|
window.addEventListener('gnubok-periodisering-toggle', customHandler)
|
|
return () => {
|
|
window.removeEventListener('storage', handler)
|
|
window.removeEventListener('gnubok-periodisering-toggle', customHandler)
|
|
}
|
|
}
|
|
|
|
/** Fire a same-tab notification so useSyncExternalStore re-subscribers
|
|
* see the change without a manual setState. */
|
|
function notifyChange() {
|
|
if (typeof window === 'undefined') return
|
|
window.dispatchEvent(new Event('gnubok-periodisering-toggle'))
|
|
}
|
|
|
|
export function PeriodiseringAutoDetectToggle() {
|
|
const enabled = useSyncExternalStore(
|
|
subscribe,
|
|
readStored,
|
|
// Server snapshot: default to enabled. Matches the client default so
|
|
// hydration is identical.
|
|
() => true,
|
|
)
|
|
|
|
const handleChange = useCallback((value: boolean) => {
|
|
try {
|
|
window.localStorage.setItem(STORAGE_KEY, String(value))
|
|
} catch {
|
|
// No-op; if storage is blocked the toggle simply won't persist.
|
|
}
|
|
notifyChange()
|
|
}, [])
|
|
|
|
return (
|
|
<SettingsRow
|
|
label="Periodisering"
|
|
help="Skannar fakturor i bokslutet efter datumintervall som sträcker sig in i nästa räkenskapsår och föreslår periodiseringar i bokslut-wizarden."
|
|
>
|
|
<Switch
|
|
id="periodisering-autodetect"
|
|
checked={enabled}
|
|
onCheckedChange={handleChange}
|
|
/>
|
|
<label htmlFor="periodisering-autodetect" className="cursor-pointer text-sm">
|
|
Aktivera automatisk periodiseringsdetektering
|
|
</label>
|
|
<SettingsRowEnd>
|
|
<Link
|
|
href="/bookkeeping/year-end/periodisering"
|
|
className="inline-flex items-center gap-1.5 text-xs text-muted-foreground transition-colors hover:text-foreground"
|
|
>
|
|
<ExternalLink className="h-3.5 w-3.5" />
|
|
Öppna periodiserings-wizarden
|
|
</Link>
|
|
</SettingsRowEnd>
|
|
</SettingsRow>
|
|
)
|
|
}
|