Jakob Wennberg
ff01640f60
* feat(reports,settings): report library + focused report routes, settings modal Reports - Replace the monolithic /reports tab-switcher with a calm, grouped report library landing (ReportLibrary + RecentReportsShelf) driven by a new lib/reports/catalog.ts. - Each report opens a focused /reports/[slug] route (FocusedReport) with a shared fiscal-year selector, optional date-range, and URL-based account drill-down into the general ledger. - Extract every report view into components/reports/views, add a reusable ReportExportMenu, and remove the old ReportsNav. Settings - Add an intercepting @settingsModal parallel route so in-app navigation to /settings opens as a modal over the current page; hard loads still resolve to the full page. - Share one SettingsShell (rail + content) between page and modal, extract each section into components/settings/sections/*Content, add a settings hotkey and command-palette entry, and remove the old SettingsSidebar. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reports,settings): remove dead salary-journal entry, fix border token Addresses PR review feedback (#629): - Remove the unreachable `salary-journal` report from the catalog. It had needsEmployees + no route + no FocusedView handler and `hasEmployees` was never plumbed through, so it never appeared in the library and a direct /reports/salary-journal URL rendered a blank frame. The report was never on the old page and has no view component; the API + generator stay in place for a proper follow-up. Drops its two now-unused i18n keys. - Replace opacity-suffixed `border-border/8` section dividers with full-opacity `border-border` across the extracted settings section components, per the design system (no opacity-suffixed border tokens on surfaces). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci: re-trigger checks (pg-real hit a Docker Hub registry timeout) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
34 lines
1.5 KiB
TypeScript
34 lines
1.5 KiB
TypeScript
import type { ComponentType } from 'react'
|
|
import { AccountSettingsContent } from './AccountSettingsContent'
|
|
import { CompanySettingsContent } from './CompanySettingsContent'
|
|
import { BookkeepingSettingsContent } from './BookkeepingSettingsContent'
|
|
import { TaxSettingsContent } from './TaxSettingsContent'
|
|
import { SalarySettingsContent } from './SalarySettingsContent'
|
|
import { InvoicingSettingsContent } from './InvoicingSettingsContent'
|
|
import { TemplatesSettingsContent } from './TemplatesSettingsContent'
|
|
import { BankingSettingsContent } from './BankingSettingsContent'
|
|
import { AssistantSettingsContent } from './AssistantSettingsContent'
|
|
import { ApiSettingsContent } from './ApiSettingsContent'
|
|
|
|
/**
|
|
* Single source of truth mapping a settings section id to the component that
|
|
* renders its content. Both the per-section route (`settings/<section>/page.tsx`,
|
|
* a thin wrapper) and the routed settings modal (`SettingsModal` → `SettingsShell`)
|
|
* resolve content through this map, so there is exactly one place a section's
|
|
* composition lives.
|
|
*/
|
|
export const SETTINGS_SECTIONS: Record<string, ComponentType> = {
|
|
account: AccountSettingsContent,
|
|
company: CompanySettingsContent,
|
|
bookkeeping: BookkeepingSettingsContent,
|
|
tax: TaxSettingsContent,
|
|
salary: SalarySettingsContent,
|
|
invoicing: InvoicingSettingsContent,
|
|
templates: TemplatesSettingsContent,
|
|
banking: BankingSettingsContent,
|
|
assistant: AssistantSettingsContent,
|
|
api: ApiSettingsContent,
|
|
}
|
|
|
|
export type SettingsSectionId = keyof typeof SETTINGS_SECTIONS
|