9 Commits

Author	SHA1	Message	Date
Ho Ngoc Hai	593d1594bd	refactor(web): replace emoji icons with lucide-react across the app ... User directive: avoid emojis for UI chrome; keep the icon language consistent with the rest of the design system (shadcn + lucide-react). Swaps ----- - lib/listing-personas.ts — Persona emojis (👨‍👩‍👧🏡🚇🧑‍💻🌳📈🛡️🏥) → Lucide icons (Baby, Home, TrainFront, Laptop, Trees, TrendingUp, Shield, HeartPulse). Persona type now carries `icon: LucideIcon`. - components/neighborhood/types.ts — POI_CATEGORY_CONFIG emojis (🏫🏥🚇🛒🍽️🌳) → Lucide (GraduationCap, Stethoscope, TrainFront, ShoppingBag, UtensilsCrossed, Trees). Config type tightened to `icon: LucideIcon`. - components/neighborhood/neighborhood-poi-map.tsx — filter pills now render <config.icon h-3.5 w-3.5>. Map markers were text-emoji (el.textContent = config.icon); replaced with hard-coded inline SVG strings per category (POI_MARKER_SVG) since lucide-static isn't installed. Marker bumped 28px → 32px for larger hit target. Popup now shows only the property name + category label (no emoji prefix). closeButton: true + closeOnClick: true for better dismissibility. - listing-detail-client.tsx — PersonaFitCard now renders <p.icon h-4 w-4 aria-hidden>. - transfer / chuyen-nhuong files — category icons (🛋️🧊🖥️🍳🛍️🏠) migrated to Lucide (Sofa, Refrigerator, Monitor, ChefHat, Store, Home) with type `icon: LucideIcon`. - Small replacements: inquiries page 📭 → Inbox; kyc page ✓ → Check. POI popup click fix ------------------- The inner SVG inside each POI marker was capturing pointer events before Mapbox's marker-click handler saw them, so clicking a marker did nothing. Explicit `innerSvg.style.pointerEvents = 'none'` lets clicks reach the wrapping .poi-marker div that setPopup() is bound to. Verified via DOM dispatch: click → popup opens with property name + category + distance + × close. Verification ------------ - Grep across the 4 scoped files for emoji code points → 0 hits. - pnpm -w test: 624/624 green. - Typecheck: no new errors in touched files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 16:01:13 +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	79e173938b	feat(avm): end-to-end AVM v2 schema + POST /analytics/valuation endpoint ... Closes the last gap from the tec-2725 branch: the valuation form's v2 extended-features section and POST endpoint can now submit real predictions through to the Python ensemble model. Backend - New DTO apps/api/src/modules/analytics/presentation/dto/predict-valuation.dto.ts with all v1 fields + 8 v2 fields (useV2 toggle, distanceToHospital/Park/ Mall in km, floodZoneRisk enum NONE|LOW|MEDIUM|HIGH, hasElevator/ Parking/Pool booleans). - New CQRS handler apps/api/src/modules/analytics/application/queries/ predict-valuation/ that routes to AVM_SERVICE.estimateValue() with the full request body. - Extend AVMParams (domain) with the same v2 fields + inline v1 fields (district, city, bedrooms, bathrooms, floors, frontage, roadWidth, hasLegalPaper, projectId, imageUrl, description, deepAnalysis). - HttpAVMService.estimateViaAi now branches on `useV2`: v2 calls the new aiClient.predictV2() → POST /avm/v2/predict on the Python service, mapping floodZoneRisk enum → 0..1 float and computing building_age_years from yearBuilt. v1 path gets all the inline descriptors wired through so non-propertyId calls no longer lose context. - AiServiceClient gets AiPredictV2Request / AiPredictV2Response types mirroring libs/ai-services/app/models/avm_v2.py::AVMv2PredictRequest (which already accepts all 7 numeric/boolean v2 fields — no Python change needed). - Register PredictValuationHandler in AnalyticsModule. - New route POST /analytics/valuation on AnalyticsController: JwtAuthGuard + QuotaGuard + EndpointRateLimitGuard (10/min), @RequireQuota('analytics_queries'), full Swagger doc. Total endpoint count 179 → 180. Frontend - Extend ValuationRequest with useV2, 3 distance-km fields, floodZoneRisk, hasElevator/Parking/Pool + export FloodZoneRisk type and FLOOD_RISK_OPTIONS. - valuationApi.predict() body mapping now includes v2 fields and renames 'areaM2' → 'area' to match the backend DTO contract. - valuationFormSchema gains matching optional Zod fields + exports FLOOD_RISK_OPTIONS for the form. - valuation-form.tsx gets: * Image upload hardening: MIME+size validation (JPG/PNG ≤5MB) before preview, role="progressbar" + aria-labels on the progress bar, role="alert" + data-testid="image-upload-error" on errors. Matches the upload-progress part of the task/tec-2725 commit 4ee0129 that was previously parked as blocked. * New Sparkles-branded "Mô hình v2 (Ensemble)" toggle alongside the existing Bot-branded "Phân tích chuyên sâu" toggle. * Collapsible "Đặc trưng mở rộng (AVM v2)" section with distance inputs, flood-risk select, and three amenity checkboxes. * handleFormSubmit passes all v2 fields through to onSubmit. Python service unchanged — AVMv2PredictRequest already has every field we send (distance_to_hospital_km, flood_zone_risk as float, has_elevator/parking/pool, etc.). Typecheck clean for the valuation surface. Pre-existing errors in metadata.spec.ts and transfer-wizard-client.tsx are unrelated and left for a follow-up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 06:49:57 +07:00
Ho Ngoc Hai	38b9def99a	feat: implement project development module, transfer management features, and industrial AVM model integration	2026-04-18 20:34:35 +07:00
Ho Ngoc Hai	24a2fd1369	fix(web,prisma): fix TypeScript errors in transfer wizard and schema ... - Fix Zod v4 enum API: replace deprecated `required_error` with `error` - Create missing TransferWizardClient component (4-step wizard: category, items, AI estimate, submit) - Add CANCELLED status to TransferListingStatus enum for soft-delete support Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-16 17:02:20 +07:00
Ho Ngoc Hai	8da488711b	feat(analytics): AVM v2 batch valuation, comparison, history + frontend upgrade ... Add batch valuation (POST /analytics/valuation/batch, max 50 properties), valuation comparison (POST /analytics/valuation/compare, 2-5 properties), and history endpoint (GET /analytics/valuation/history/:propertyId) with confidence explanation helper. Frontend: enhanced valuation form with project autocomplete and deep analysis toggle, results with confidence badges and price range visualization, comparables table, history chart, market context card, and PDF export. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-16 05:08:05 +07:00
Ho Ngoc Hai	3c6ed4c82a	feat(web): add Property Valuation UI with AVM integration ... Build the valuation page at /dashboard/valuation with form input, AI-powered price estimation results, comparable properties display, and valuation history. Add "Dinh gia AI" button to listing detail sidebar for quick per-listing estimates. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-09 00:17:12 +07:00
Ho Ngoc Hai	207a2013f3	feat(listings-frontend): add create/edit form, detail page, and listing components ... - Multi-step wizard for listing creation (basic info, location, details, pricing, images) - Listing detail page with image gallery, property specs, seller/agent info, stats - Listings index page with filters (transaction type, property type) and pagination - Edit page with tab-based form (read-only until backend PATCH endpoint available) - Drag & drop image upload component with preview and multi-file support - Dashboard layout with navigation bar - New UI primitives: textarea, select, badge, tabs - Listings API client with typed endpoints matching backend contract - Zod validation schemas for all form steps - Status badges with Vietnamese labels for all listing states - Responsive design across all pages Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-08 01:54:08 +07:00
Ho Ngoc Hai	0b29fac35e	feat(notifications): add multi-channel notification module with Email, FCM, templates, and event listeners ... - Domain: NotificationLog/NotificationPreference entities, repositories, channel value object - Infrastructure: EmailService (nodemailer/SMTP), FcmService (firebase-admin), TemplateService (Handlebars) - Application: SendNotification CQRS command, UserRegistered + AgentVerified event listeners - Presentation: NotificationsController with history, preferences, and templates endpoints - Prisma: NotificationLog and NotificationPreference models with proper indexes - Templates: Vietnamese notification templates for user.registered, agent.verified, listing.approved, inquiry.received, password.reset Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-08 01:42:17 +07:00