Files
TehRiehlDeal 062b807732
CI / secrets-scan (push) Successful in 7s
CI / sast (push) Successful in 15s
CI / vuln-scan (push) Successful in 16s
CI / test (push) Successful in 28s
CI / lint (push) Successful in 34s
CI / build-images (push) Successful in 2m7s
CI / image-scan (push) Successful in 55s
CI / push (push) Has been skipped
CI / secrets-scan (pull_request) Successful in 7s
CI / sast (pull_request) Successful in 15s
CI / vuln-scan (pull_request) Successful in 16s
CI / test (pull_request) Successful in 26s
CI / lint (pull_request) Successful in 33s
CI / build-images (pull_request) Successful in 2m4s
CI / image-scan (pull_request) Successful in 53s
CI / push (pull_request) Has been skipped
Fix ImportStatementDialog overflow on narrow viewports
The review and confirm steps were rendering as wide editable tables
inside a `sm:max-w-3xl` dialog (~768px). The inputs alone consumed
~750px before padding, so on smaller desktop windows the content was
clipped left/right, and on mobile it was effectively unusable.

Two-pronged fix:

- Widen the dialog itself to `md:max-w-5xl xl:max-w-6xl` so the table
  has room on typical desktops. Mobile stays full-width minus margin.
- Split each step into responsive layouts gated by Tailwind's `md:`
  breakpoint. Desktop keeps the editable table (now with fixed-width
  columns, an inline status badge instead of a separate Status column,
  and `overflow-auto` as a graceful fallback at intermediate widths).
  Below `md:`, rows render as stacked cards — checkbox + date + status
  on top, description full-width, amount + type wrapped, transfer
  destination dropping below when applicable. Same data, no horizontal
  scrolling on phones.

The Confirm step's expand-to-preview table gets the same treatment:
table on desktop, summary cards on mobile.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 15:44:33 -07:00
..
2026-05-04 16:20:23 -07:00
2026-05-04 16:20:23 -07:00

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:

export default defineConfig([
  globalIgnores(['dist']),
  {
    files: ['**/*.{ts,tsx}'],
    extends: [
      // Other configs...

      // Remove tseslint.configs.recommended and replace with this
      tseslint.configs.recommendedTypeChecked,
      // Alternatively, use this for stricter rules
      tseslint.configs.strictTypeChecked,
      // Optionally, add this for stylistic rules
      tseslint.configs.stylisticTypeChecked,

      // Other configs...
    ],
    languageOptions: {
      parserOptions: {
        project: ['./tsconfig.node.json', './tsconfig.app.json'],
        tsconfigRootDir: import.meta.dirname,
      },
      // other options...
    },
  },
]);

You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:

// eslint.config.js
import reactX from 'eslint-plugin-react-x';
import reactDom from 'eslint-plugin-react-dom';

export default defineConfig([
  globalIgnores(['dist']),
  {
    files: ['**/*.{ts,tsx}'],
    extends: [
      // Other configs...
      // Enable lint rules for React
      reactX.configs['recommended-typescript'],
      // Enable lint rules for React DOM
      reactDom.configs.recommended,
    ],
    languageOptions: {
      parserOptions: {
        project: ['./tsconfig.node.json', './tsconfig.app.json'],
        tsconfigRootDir: import.meta.dirname,
      },
      // other options...
    },
  },
]);