Update property.js#123
Open
SaikatDash wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for smartrentsystem canceled.Built without sensitive environment variables
|
hitesh-kumar123
pushed a commit
that referenced
this pull request
Jan 21, 2026
--- Name : "Fix price range validation for filter modal" about: Submit changes for review title: "PR: [Improves minimum and maximum price validation, displays appropriate error messages]" labels: "SWoC" assignees: "" --- ## 📌 Linked Issue <!-- Link to the issue this PR addresses (e.g. "Closes #123" or "Related to #456") --> - [ ] Connected to #26 --- ## 🛠 Changes Made <!-- Bullet-point summary of your changes --> - Fixed: Prevented negative values from being accepted in price range inputs and added appropriate validation error messages. - Refactored: Removed no-op debug forEach blocks to clean up unnecessary code. - Verified: Reviewed and validated filter modal behavior across all relevant pages. --- ## 🧪 Testing <!-- How did you verify your changes? --> - [ ] Ran unit tests (`npm test`) - [x] Tested manually (describe below): - Entered negative values in the price range fields on the listings page → validation error message is displayed and values are rejected. - Entered valid minimum and maximum prices → filters are applied. - Entered invalid price ranges (min > max or out-of-range values) → validation error message is displayed and values are rejected. --- ## 📸 UI Changes (if applicable) <!-- Before/after screenshots or GIFs --> ### Before https://github.com/user-attachments/assets/f9628ecb-f771-47e3-b647-94cab369196f ### After https://github.com/user-attachments/assets/0b6eacdb-5b1d-4144-8db3-569dc0beffe4 --- ## 📝 Documentation Updates - [ ] Updated README/docs - [ ] Added code comments --- ## ✅ Checklist - [x] Created a new branch for PR - [x] Have stared the repository - [x] Follows [JavaScript Styleguide](CONTRIBUTING.md#javascript-styleguide) - [x] No console warnings/errors - [x] Commit messages follow [Git Guidelines](CONTRIBUTING.md#git-commit-messages) ## 💡 Additional Notes (If any) <!-- Optional: Deployment needs, breaking changes, etc. -->
hitesh-kumar123
pushed a commit
that referenced
this pull request
Feb 11, 2026
--- name: "📦 Pull Request" about: Submit changes for review title: "PR: [Brief Description]" labels: "" assignees: "" --- ## 📌 Linked Issue <!-- Link to the issue this PR addresses (e.g. "Closes #123" or "Related to #456") --> - [x] Connected to #166 --- ## 🛠 Changes Made <!-- Bullet-point summary of your changes --> - **Added**: Enhanced "Stay Anywhere" section with modern UI design - **Added**: 2 new property types (Beach and Luxury) expanding from 4 to 6 total - **Added**: Interactive hover effects with smooth animations and transitions - **Added**: Premium badge for Luxury properties with gradient styling - **Added**: Stay count indicators with home icons for each property type - **Added**: "View all property types" call-to-action button - **Updated**: Responsive grid layout (2-3-6 columns for mobile-tablet-desktop) - **Updated**: Card design with white background, shadows, and better spacing - **Updated**: Typography hierarchy with improved font weights and sizes - **Improved**: User engagement with hover arrows and scale transformations --- ## 🧪 Testing <!-- How did you verify your changes? --> - [ ] Ran unit tests (`npm test`) - [x] Tested manually (describe below): - **Test case 1**: Verified responsive design across different screen sizes - Steps: Resized browser window from mobile to desktop view - Expected Result: Grid layout adapts correctly (2→3→6 columns) - **Test case 2**: Tested hover interactions on property cards - Steps: Hovered over each property type card - Expected Result: Smooth zoom, shadow effects, and arrow icons appear - **Test case 3**: Verified navigation functionality - Steps: Clicked on property type cards and CTA button - Expected Result: Proper navigation to listings page with correct filters --- ## 📝 Documentation Updates - [ ] Updated README/docs - [x] Added code comments for new translation strings --- ## ✅ Checklist - [x] Created a new branch for PR (`feat/ui-stay-anywhere-166`) - [ ] Have stared the repository - [x] Follows [JavaScript Styleguide](CONTRIBUTING.md#javascript-styleguide) - [x] No console warnings/errors - [x] Commit messages follow [Git Guidelines](CONTRIBUTING.md#git-commit-messages) ## 💡 Additional Notes (If any) <!-- Optional: Deployment needs, breaking changes, etc. --> - **New translation strings added**: `beachText`, `coastalLivingText`, `luxuryText`, `premiumExperienceText`, `uniqueText`, `oneOfAKindText` - **No breaking changes**: All existing functionality preserved - **Performance**: Optimized image loading and smooth CSS transitions - **Accessibility**: Maintained proper semantic HTML and ARIA labels
hitesh-kumar123
pushed a commit
that referenced
this pull request
Feb 16, 2026
…#176) --- name: "📦 Pull Request" about: Submit changes for review title: "PR: changed location and linked linkedin to direct to the correct profile]" labels: "swoc26" assignees: " @stargalax " --- ## 📌 Linked Issue <!-- Link to the issue this PR addresses (e.g. "Closes #123" or "Related to #456") --> - [ ] Connected to #175 --- ## 🛠 Changes Made <!-- Bullet-point summary of your changes --> - Added: Location , takes users to linkedin when clicked --- ## 🧪 Testing <!-- How did you verify your changes? --> - [✓] Ran unit tests (`npm test`) - [✓] Tested manually (describe below): --- ## 📸 UI Changes (if applicable) <!-- Before/after screenshots or GIFs --> Before <img width="527" height="472" alt="image" src="https://github.com/user-attachments/assets/27eff134-990f-4ae4-b1d1-96fcce853496" /> After <img width="1852" height="475" alt="image" src="https://github.com/user-attachments/assets/e3d4e189-661f-403e-821e-95d98b880976" /> <img width="531" height="571" alt="image" src="https://github.com/user-attachments/assets/91048398-ff94-4cdf-8f5f-58f887b706da" /> clicking linkedin icon:  --- ## 📝 Documentation Updates - [ ] Updated README/docs - [ ] Added code comments --- Changes made in contact.jsx (line 111,112) and in footer.jsx(line 104, 229) ## ✅ Checklist - [✓] Created a new branch for PR - [✓] Have stared the repository - [✓] Follows [JavaScript Styleguide](CONTRIBUTING.md#javascript-styleguide) - [✓] No console warnings/errors - [✓] Commit messages follow [Git Guidelines](CONTRIBUTING.md#git-commit-messages) ## 💡 Additional Notes (If any) <!-- Optional: Deployment needs, breaking changes, etc. -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
name: "📦 Pull Request"
about: Submit changes for review
title: "PR: Update property model for location-based search"
labels: enhancement
assignees: ""
📌 Linked Issue
🛠 Changes Made
locationfield to store latitude and longitude.city,state, andareafields for text-based location search.property.jsMongoose schema to support geospatial queries.🧪 Testing
npm test)Steps: Create a property with valid latitude and longitude
Expected Result: Property is saved successfully in MongoDB.
Steps: Query properties using
$neargeospatial searchExpected Result: Nearby properties are returned correctly.
📝 Documentation Updates
property.js✅ Checklist
2dsphereindex added💡 Additional Notes
locationcan be migrated gradually.