Bug #2928
Proposed Location Module and setup
Description
Proposed Location Module and setup
Updated by Saransh Bakoliya about 2 months ago
I have done this work today:
Worked on creating and structuring the new Property Reporting page layout.
Worked on updating Google Map styling to a clean white theme.
Worked on adding a Custom option inside the radius selection dropdown.
Worked on creating a numeric input box for entering custom radius values.
Worked on fixing text overlapping issues inside the custom radius box.
Worked on removing the radius field from the main filter card.
Worked on replacing State, City, and Nearby City dropdowns with simple text input boxes.
Worked on auto-searching so Google Map automatically zooms to the typed location.
Worked on setting map search bar text to "Search address...".
Worked on making the Google Map popup modal bigger, wider, and taller.
Worked on adding proper spacing between controls so titles do not touch top borders.
Worked on connecting main page search filters to load location data.
Worked on connecting property details view to display full location info.
Worked on connecting media section to show location photos and videos.
Worked on connecting activity log section to display location history.
Worked on making Apply buttons instantly fetch and update search results on click.
Worked on fixing double loading issues so search runs only once per click.
Updated by Shreya Agarwal about 2 months ago
Today, I implemented the complete Proposed Locations management feature into the application. We created the interactive AddProposedLocationDrawer component to capture property details, owner contact info, client & proposed offers, amenities, and file uploads. Location selection was enhanced by integrating DirectGoogleMap with automatic address reverse-geocoding to auto-populate city, state, country, and postal code fields. We built proposedLocationService to handle API endpoints for creating locations, media uploads, adding notes, and updating onboarding statuses. Additionally, we created ProposedLocationsPage with a search and table view, and integrated the new route (/proposed-locations) within RoleBasedRouter.
Updated by Saransh Bakoliya about 2 months ago
Today i have worked on ->
Cleaned activity log text by removing underscores and formatted dates to match date picker standards.
Filtered activity log data to display BBM user entries while excluding tenant-admin logs.
Connected activity log components dynamically to live backend API endpoints.
Removed hardcoded dummy data from PropertyReportingPage for pure dynamic API rendering.
Fixed API call triggers and resolved error handling on media upload workflows.
Optimized proposed location service API methods for clean sequential execution.
Updated granular permission checks across Proposed Location modules.
Removed unnecessary UI directional arrows and stopped unintended background API calls.
Implemented CSS concentric wave ripple pulse animations radiating from map pins.
Synchronized pin wave animations across both the drawer and location radius picker modal.
Replaced State text filter with a searchable Autocomplete dropdown prefilled with Indian states.
Fixed missing map pin issue by implementing native Google Maps red teardrop pin markers.
Ensured map markers remain visible and correctly anchored upon location selection.
Fixed API filter bug to send numeric latitude, longitude, and radiusKm instead of address text strings.
Verified request parameters and DTO response mapping against live Swagger API documentation.
Created PropertyLocationViewModal for clean view-only map viewing without search bar, radius, or pin drag.
Resolved 502 Bad Gateway errors on location creation by removing failing media POST upload loop.
Removed latitude/longitude text from main table Location Name column while retaining interactive view drawer map.
Updated by Shreya Agarwal about 2 months ago
Building on yesterday's complete Proposed Locations feature implementation so Today continue focused on refining the AddProposedLocationDrawer UI to match the project's design system. Updated the drawer width to 90% with responsive breakpoints, standardized all input fields with 56px height and border-radius 3, and added section headers with colored icon circles for better visual hierarchy. Implemented hover effects across all Paper sections with smooth lift, shadow, and border color transitions. Optimized the layout with fields arranged in 2-3 column grids (Location Name + Type, Google Location + Latitude + Longitude, Owner Name + Contact + Email) for better space utilization. Enhanced the header close button with scale animation on hover and removed design token dependencies for cleaner styling.
Updated by Saransh Bakoliya about 1 month ago
Today i worked on ->
Fixed DatePicker 10px rounded border radius in Session Remark Reports.
Removed User ID filter field from Customer Support Audit tab.
Updated Session Remark Reports permissions to session-remark-audit.view & session-remarks.view.
Fixed missing hasPermission TypeScript error in Session Remark Reports page.
Updated Proposed Locations permissions strictly to network_expansion_visits.view & manage.
Bound Land Type table column directly to API propertyType response.
Added mapping fallbacks for all backend property type field variations (propertyType, property_type, type).
Made Land Type filter dropdown options dynamically load from API data.
Resolved TypeScript type error for Land Type filter state assignment.
Fixed API query parameter bug that returned zero results when clicking Apply.
Implemented case-insensitive Land Type filtering so Apply button displays matching properties in the table.