Skip to content

[FRONTEND] Apply consistent standards to booking date logic #927

@jji05

Description

@jji05

Is your feature request related to a problem? Please describe.

Received feedback from users that state the current booking calendar is not as consistent compared to other booking sites.

Typically the end date of a user selected booking marks the date as the checkout (I.e you leave at 10/11am in the morning of the checkout date), although in our case, our end date considers the next morning as the checkout date.

By making this change, it prevents the ambiguity as to when a checkout is, and provides a more consistent standard across booking sites.

Image

Describe the solution you'd like

The booking end date should be shifted by 1 day and be marked as the morning, instead of the booking end date actually being the night you sleep into.

Additional context

BEFORE MERGING

  • Storybooks created where possible
  • Tested with nock if data fetching
  • Tests written for critical interactions
  • PR Reviewed (For non-trivial changes)
  • Changes tested after rebasing on master or merging in master (hint: git fetch origin master:master, then git rebase master or git merge master)
  • All required PR checks passing

Metadata

Metadata

Assignees

No one assigned

    Labels

    frontendrelating to code in the /client directory

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions