9 Commits

Author	SHA1	Message	Date
Ho Ngoc Hai	283984b2f2	feat(listings): Mapbox location picker in create + edit forms ... User feedback: typing lat/lng by hand is painful — wire a real map picker. New component apps/web/components/map/location-picker.tsx: - Mapbox map with theme-synced style (uses useMapboxStyle). - Draggable primary marker (custom pin, inner-wrapped so Mapbox's translate isn't clobbered — follows the hover-fix pattern we shipped last commit). - Click anywhere on the map → marker jumps + onChange fires. - Dragend → onChange fires. - Search box using Mapbox Geocoding API (/geocoding/v5/mapbox.places) scoped to country=vn, language=vi, limit=5, debounced 350ms with AbortController. Clicking a suggestion centers the map + fills the resolved { address, ward, district, city } from feature.context. - Graceful fallback when NEXT_PUBLIC_MAPBOX_TOKEN is missing. - Inline help "Nhấp vào bản đồ hoặc kéo pin để chọn vị trí". StepLocation (listing-form-steps.tsx): - New optional `setValue` + `watch` props. When both are passed the picker renders and wires lat/lng (+ address/ward/district/city from geocoder) into the form. Without them, the Step falls back to the manual-only layout (kept for callers that don't want the picker). - Dynamic-import the picker with ssr:false so mapbox-gl stays out of the server bundle. Wired into: - /listings/new page — picker enabled on Step 2 (Vị trí). - /listings/[id]/edit page — picker enabled on the Location tab, with latitude/longitude now hydrated from property.latitude/longitude. Test fixture update: listing-form-steps.spec.tsx no longer asserts the placeholder string — instead verifies the lat/lng inputs still render when the picker is absent (setValue not supplied), matching the new opt-in contract. Verification - Typecheck clean across touched files. - 624 / 624 web tests pass. - Preview smoke: /listings/<id>/edit → Vị trí tab renders map + draggable pin + search, lat/lng prefilled from listing data. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 17:55:26 +07:00
Ho Ngoc Hai	6b783c357d	feat(listings+projects): wire listing PATCH + project rich content parity ... Two CRUD/parity gaps closed: Listings edit — PATCH was dead-ended at the frontend ---------------------------------------------------- Backend PATCH /listings/:id existed and accepted Phase B fields but the dashboard edit page was read-only with a disclaimer stub. Now: - listings-api.ts exports UpdateListingPayload (Partial<CreatePayload>) and listingsApi.update(id, data). - /listings/[id]/edit/page.tsx wires handleSubmit → maps the form to UpdateListingPayload (coerces numerics, splits CSV amenities/view/ suitableFor, normalises petFriendly 3-way select), calls update, shows green success banner or red error banner. Removed the disclaimer text. - Form footer now has Huỷ + Lưu thay đổi buttons. Projects rich content — parity with Phase B listings --------------------------------------------------- Same "Phù hợp với ai / Vì sao nên chọn dự án này" pattern now on project detail. Schema - ProjectDevelopment: suitableFor String[] @default([]) + whyThisLocation String? @db.Text. Migration 20260419100000 applied via db:push. Backend - CreateProjectDto / UpdateProjectDto pick up optional suitableFor + whyThisLocation (MaxLength 2000). - CreateProjectCommand / UpdateProjectCommand append the two trailing args; handlers forward them. - ProjectDevelopment entity carries the props + updateDetails branches. - ProjectListItem (inherited by ProjectDetailData) exposes both. - Prisma repo writes them on raw INSERT/UPDATE and reads them in toDomain + toListItem. Controller passes dto → commands. Frontend - du-an-api.ts: ProjectDetail / CreateProjectPayload / UpdateProjectPayload gain suitableFor + whyThisLocation. duAnApi exports create / update / delete (already landed earlier, now in sync with the new fields). - du-an-server.ts normalizer pulls the two fields safely (filter strings, default empty array / null). - Dashboard /projects/new + /projects/[id]/edit: new "Phù hợp & lý do khu vực" form section (CSV split + 2000-char textarea). Submit handlers forward to create/update payloads. - Public /du-an/[slug] detail (du-an-detail-client.tsx): two new cards just below the quick-stats grid — * ProjectPersonaFitCard: chips for each suitableFor label with a "Chủ đầu tư chọn" badge (bg-primary/10), plus a disabled <Button><Sparkles /> AI nhận định dự án (sắp ra mắt)</Button> teaser with a TODO pointing to a future project-AI advisor endpoint. * ProjectWhyLocationCard: renders whyThisLocation in whitespace-pre-wrap; skipped when the field is empty. Verification - API typecheck clean; 1975/1975 tests pass. - Web typecheck clean in touched files; 624/624 tests pass. - Lucide-only icons; Vietnamese labels; no new npm packages; runtime imports preserved for NestJS-DI classes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 16:33:54 +07:00
Ho Ngoc Hai	88429a1e51	feat(listings): phase B — rich property fields + admin-authored personas ... Schema (prisma/migrations/20260419000000_property_rich_fields) -------------------------------------------------------------- New Prisma enums: - Furnishing: FULLY_FURNISHED / BASIC_FURNISHED / UNFURNISHED - PropertyCondition: NEW / LIKE_NEW / RENOVATED / USED New Property columns (all optional / default empty, no data loss): - furnishing, propertyCondition — enums above - balconyDirection — reuses existing Direction enum - maintenanceFeeVND BigInt (phí quản lý/tháng) - parkingSlots Int - viewType String[] (e.g. ["Sông","Thành phố"]) - petFriendly Boolean (null = unknown) - suitableFor String[] — admin-chosen persona labels - whyThisLocation Text — admin narrative Backend wiring end-to-end ------------------------- - Create/Update DTOs: @IsEnum/@IsString/@IsNumber/@IsBoolean/@IsArray validators; maintenanceFeeVND accepted as a numeric string, cast to BigInt on the way to Prisma. whyThisLocation capped at 2000 chars. - Introduced a small `PropertyExtras` interface on the create/update commands so the constructor signature stays readable instead of ballooning to 30+ positional args. Handlers forward it to the repo. - Prisma property repository writes all new columns via raw SQL INSERT/UPDATE and reads them on findById. - ListingDetailData + findByIdWithProperty expose the 9 new fields (maintenanceFeeVND serialised as decimal string to avoid BigInt JSON). Frontend -------- - listings-api.ts: ListingDetail.property + CreateListingPayload carry the 9 new fields; Furnishing + PropertyCondition exported as string unions. - validations/listings.ts: zod schema extended; FURNISHING_OPTIONS, PROPERTY_CONDITION_OPTIONS, VIEW_TYPE_OPTIONS label arrays added in the existing DIRECTIONS style (Vietnamese labels). - listing-form-steps.tsx StepDetails: new "Nội thất & điều kiện" fieldset with selects/inputs for each field. viewType + suitableFor are comma-separated text (same convention as amenities). petFriendly is a 3-way select (không chọn / Có / Không). - new/page.tsx + [id]/edit/page.tsx: submit handlers split CSV inputs into arrays, coerce petFriendly, prune empty selects. - listing-detail-client.tsx Details card: new rows for furnishing, propertyCondition, balconyDirection, maintenanceFeeVND (VND formatted), parkingSlots, viewType (joined · ), petFriendly (Cho phép / Không cho phép / hide when null). - PersonaFitCard now takes the listing directly and MERGES admin suitableFor (rendered first with a "Người đăng chọn" badge in primary accent) with the derived personas (deduped by label). When whyThisLocation is non-empty it overrides the derived narrative. Tests ----- - listing-detail-client.spec.tsx fixture gains all 9 nullable/empty defaults. - listing-form-steps.spec.tsx direction-options duplication fixed. - pnpm --filter @goodgo/api test --run: 1975/1975 pass. - pnpm --filter @goodgo/web test --run: 624/624 pass. Phase B of 4. Next: Phase E AI advisor via Anthropic Opus (URL+key to be provided by the user). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 15:08:04 +07:00
Ho Ngoc Hai	ba0bf97426	feat: dashboard CRUD for Projects + Industrial Parks, listings delete, BĐS homepage card ... Backend — DELETE endpoints (hard delete, ADMIN or owner): - DELETE /projects/:id (Admin) — new DeleteProjectCommand/Handler, repository.delete() adapter, module wiring. - DELETE /industrial/parks/:id (Admin) — same pattern. - DELETE /listings/:id (JWT + owner-or-Admin check in handler). Frontend — API clients: - lib/du-an-api.ts: add create/update/delete + CreateProjectPayload, UpdateProjectPayload types. - lib/khu-cong-nghiep-api.ts: add createPark/updatePark/deletePark + Create/Update payload types. - lib/listings-api.ts: add delete(). Dashboard pages — new: - /projects (Quản lý dự án): list with filters + edit/delete actions, /projects/new form (sectioned Cards, zod-validated), /projects/[id]/edit with danger-zone delete. - /industrial-parks (Quản lý KCN): same triad. Fix occupancy-rate display (percentage already 0-100, no need to *100). Dashboard listings page: - Add Edit/Delete row actions with confirm + useMutation; error banner on mutation failure. Table view gains a "Thao tác" column; list view gains a footer action bar below each card. Dashboard nav: - Catalog group: /du-an → /projects (Quản lý dự án), /khu-cong-nghiep → /industrial-parks (Quản lý KCN). Desktop primaryNav updated too. Public homepage: - Add "Bất động sản" as a 5th feature card/tab → /search, using listingsApi for the "Featured listings" section. - Bump grid to lg:grid-cols-5, update features subtitle copy ("Năm/Five core services"). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 10:37:33 +07:00
Ho Ngoc Hai	2f07b374d9	feat(web): dashboard gets Dự án + KCN nav; listings pages use list layout ... Three asks after a walk-through of the dashboard: 1. Dashboard navigation was missing direct entry points to the two catalog surfaces (Dự án, Khu Công Nghiệp) even though both exist at /du-an and /khu-cong-nghiep. Users landing in the dashboard had to go back out to the public header to reach them. 2. The "Tin đăng" (dashboard listings) page defaulted to a 3-column grid which shows only a handful of properties per viewport. Scanning many listings at once is easier as a vertical list of horizontal rows. 3. The public /search results used the same 3-column grid via PropertyCard. Asked to flip to list there too. Changes - (dashboard)/layout.tsx: new `catalogs` nav group with Building2 + Factory icons pointing at /du-an and /khu-cong-nghiep. Primary desktop nav also exposes both so they're reachable without opening the hamburger. Uses existing `nav.projects` / `nav.industrialParks` i18n keys plus a new `dashboard.catalogs` label in vi/en. - (dashboard)/listings/page.tsx: default viewMode flipped from 'grid' to 'list'. The list mode renders a horizontal row per listing (thumbnail + title/location + price + badges + engagement counters) inside an <ul>. Toggle button relabelled "Danh sách". - components/search/search-results.tsx + property-card.tsx: add a `layout?: 'card' | 'list'` prop to PropertyCard. When `list`, the card renders as a horizontal row with 224px thumbnail on sm+, stacked on mobile. SearchResults wraps items in a <ul><li> and asks for list layout. Default card layout preserved so other callers (compare, related, etc.) keep their vertical card view. No API / DB changes. Typecheck clean for the touched surfaces. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 09:49:51 +07:00
Ho Ngoc Hai	a9fa214544	feat: comprehensive seed, Lucide icons, grouped dashboard nav, API fixes ... - Rewrite prisma/seed.ts to populate all 27 models with realistic Vietnamese real estate data (8 users with login, 10 properties, 10 listings, orders, payments, reviews, notifications, etc.) - Replace all emoji icons with Lucide React SVG icons across frontend for consistent rendering, sizing, and accessibility - Redesign dashboard nav: grouped sidebar with section headers, primary/secondary split on desktop, icon-only secondary items - Replace language switcher flag emoji with Globe icon - Replace SVG theme toggle with Lucide Moon/Sun icons - Fix API startup: graceful fallback for Sentry profiling, Google OAuth, and Zalo OAuth when credentials are not configured - Relax rate limiting in development mode (10k req/min) - Fix listings API to include media[] array in search response - Add optional chaining for property.media across frontend components - Update OAuth strategy tests to match graceful fallback behavior Co-Authored-By: Claude Opus 4 (1M context) <noreply@anthropic.com>	2026-04-13 11:13:04 +07:00
Ho Ngoc Hai	759052a71f	fix(web): update dashboard pages, layouts, and listing forms ... Update 12 page/layout files across auth, dashboard, listings, and search routes to improve type safety, fix component imports, and align with latest API changes. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-11 01:39:59 +07:00
Ho Ngoc Hai	55a01c5738	feat(web): centralise Vietnamese price formatting across all pages ... Create a single `currency.ts` utility with `formatPrice`, `formatVND`, `formatPricePerM2`, and `parseVND` to replace 9+ duplicated inline formatters. This fixes inconsistent decimal handling (1.5M was truncated to "1 triệu") and standardises price/m² display. Integrated across property cards, listing detail, dashboard, analytics, payments, pricing, and admin moderation pages with 19 new unit tests. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-10 23:33:31 +07:00
Ho Ngoc Hai	7195064f12	feat(web): add i18n locale routes and language switcher component ... Add locale-prefixed routes for admin, auth, dashboard, and public pages. Add error, loading, and not-found pages for locale context. Add language switcher UI component for Vietnamese/English toggle. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-09 09:44:18 +07:00