wrongmove/frontend
Viktor Barzin 9a5ad7878c wrongmove: preserve heatmap color on multi-property popup + arrow nav on card carousel
When the user clicks a heatmap hex that contains multiple properties,
each property card in the resulting popup now renders a left-edge
color stripe matching the heatmap gradient for that property's
individual value of the active metric (Price/m², Total Price, Size,
Bedrooms, …). The "color code" carries from the map into the popup
instead of dying at the hex boundary.

Plumbing:
- `colorSchemes.ts` gains `interpolateMetricColor(value, min, max, stops)`
  that walks the color-stop ramp and returns `rgb(R, G, B)`.
- `Map.tsx` stashes the latest `{min, max}` from `computeColorScale` in
  a ref so `getListingDialog` can compute per-property colors without
  re-running the worker.
- `PropertyCard` accepts an optional `metricColor` prop and applies it
  as a 4px `border-left`. Compact variant unchanged (no stripe).

Also resolves the Round-3 Fix-4 follow-up: `CardCarousel` (inside
PropertyCard.tsx) now has clickable prev/next chevron buttons in
addition to drag + keyboard navigation. Buttons fade in on hover
(group-hover) and are always focus-visible for keyboard users; clicks
stop propagation so the parent card click handler doesn't fire.

Tests: 9 new (4 covering interpolateMetricColor edge cases —
null/NaN/clamp — and 4 covering metricColor stripe + carousel
buttons present/absent). Full suite 210/210.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-15 23:10:20 +00:00
..
public Move hexgrid heatmap computation to Web Worker 2026-02-22 15:04:37 +00:00
src wrongmove: preserve heatmap color on multi-property popup + arrow nav on card carousel 2026-05-15 23:10:20 +00:00
.dockerignore Expand frontend .dockerignore to exclude build artifacts 2026-02-21 19:51:04 +00:00
.env.sample Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
.gitignore wrongmove: write VITE_MAPBOX_TOKEN to .env.production in CI (replaces broken build_args) 2026-05-15 22:10:25 +00:00
Caddyfile.dev Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
components.json Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
Dockerfile wrongmove: write VITE_MAPBOX_TOKEN to .env.production in CI (replaces broken build_args) 2026-05-15 22:10:25 +00:00
eslint.config.js Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
index.html Move hexgrid heatmap computation to Web Worker 2026-02-22 15:04:37 +00:00
nginx.conf Fix stale browser cache after redeployment with proper nginx cache headers 2026-02-08 22:51:11 +00:00
package-lock.json chore: add react-router-dom dependency for URL-based navigation 2026-02-28 15:58:39 +00:00
package.json chore: add react-router-dom dependency for URL-based navigation 2026-02-28 15:58:39 +00:00
README.md Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
start.sh Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
tsconfig.app.json Move hexgrid heatmap computation to Web Worker 2026-02-22 15:04:37 +00:00
tsconfig.app.tsbuildinfo wrongmove: guard property cards against null backend fields (fix BUY crash) 2026-05-10 21:17:41 +00:00
tsconfig.json Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
tsconfig.node.json Remove JS obfuscator that broke Mapbox GL map rendering 2026-02-08 22:47:01 +00:00
tsconfig.node.tsbuildinfo Flatten repo structure: move crawler/ to root, remove vqa/ and immoweb/ 2026-02-07 23:01:20 +00:00
vite.config.ts Remove JS obfuscator that broke Mapbox GL map rendering 2026-02-08 22:47:01 +00:00
vitest.config.ts Fix frontend CI pipeline OOM kills and test timeouts 2026-02-17 21:46:29 +00: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:

Expanding the ESLint configuration

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

export default tseslint.config({
  extends: [
    // 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,
  ],
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})

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 tseslint.config({
  plugins: {
    // Add the react-x and react-dom plugins
    'react-x': reactX,
    'react-dom': reactDom,
  },
  rules: {
    // other rules...
    // Enable its recommended typescript rules
    ...reactX.configs['recommended-typescript'].rules,
    ...reactDom.configs.recommended.rules,
  },
})