Amaresh taking over for Alisha - feat(listing-overview): add listing overview backend implementation

[alishawalunj]

Description

Related PRS (if any):

This backend PR is not related to any backend PR.

Main Changes

• Configured schema for the Bookings collection.
• Implemented controller functionalities:
  • Get Listing Overview
  • Submit Booking
• Configured routes for both APIs.

How to Test

1. Checkout this branch.
2. Run npm install and start the server (e.g., npm run dev).
3. Test the endpoints in Postman or your API client:

Get Listing Overview

• URL: http://localhost:4500/api/lb/listOverview/68c5e69e7b6edc12ba7402cc
• Additional listing IDs to test:
  681fdece9b28a081622ba76c, 681fdee39b28a081622ba76e

Submit Booking Request

• URL: http://localhost:4500/api/lb/submitBooking
• Request Body:

{
  "listingId": "68c5e69e7b6edc12ba7402cc",
  "rentingFrom": "2025-10-28",
  "rentingTill": "2025-10-29"
}

4. Verify that date validation works:
   • rentingFrom must be before rentingTill.
   • Overlapping bookings should return a conflict error.
   • Successful bookings return a confirmation with the booking ID.

Screenshots or videos of changes:

[akshith312]

Tested PR locally.
Checked the endpoints for different properties.
All the end points work as expected.

Conflict on booking dates: Successful Booking: Date Check:

[DeepighaJ]

Checked out to current branch and tested PR locally. The Get Listing overview works as expected. But the Submit book request gives 400 Bad request stating "message": "Missing required fields: listingId, rentingFrom, rentingTill" so couldnt validate the date and conflict error validations.

[amaresh2001]

@DeepighaJ Use raw format in the Body tab as JSON instead of Text in the dropdown. Could you please re-review when you get a chance? Thank you!

If you use an invalid date range, a message will be returned

[kzou55]

I ran the current branch locally, and I can verify the following works:

• Get listing overview
  

• Submit successful booking
  

• Invalid Date Range Error

• Booking Conflict

Issues:

• Error message for bad date value for "rentingTill" field is fine
  
  However, the return message isn't correct if the "rentingFrom" field is a bad date value

  

[amaresh2001]

@kzou55 Fixed the invalid date value issue. Added explicit Number.isNaN() validation for both rentingFrom and rentingTill before any DB operations, so bad date values now return a proper 400 with the
correct field name instead of a 500 Mongoose cast error. Tested locally and confirmed:

• Bad rentingFrom → 400 "Invalid date value for rentingFrom"
• Bad rentingTill → 400 "Invalid date value for rentingTill"

Could you please re-review when you get a chance? Thank you!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[kzou55]

Hi Amaresh,

I retested the PR again and I verified that get listing overviews, submitting book request and date validation works.

• Get Listing Overview

  • Valid IDs
    
    
    
  • Invalid Listing ID:
    

• Submit Booking Request

  • Correct submit booking request
    

  • Invalid Listing ID
    

  • Booking conflict
    

  • Missing Fields
    

  • Invalid renting from and renting till dates
    
    

  • rentingFrom must be before rentingTill