Add Itinerary Event Component

cpilande commented 10 months ago

Description

This PR creates the itinerary event component that will be placed inside of the itinerary. In this component, there are fields available for the event characteristics.

Date
Time
Location
Guest Number

Motivation and Context

This component showcases the event information that the user is scheduling. The user can see all essential information at a glance in an easily readable way.

Further Expansion of Feature

Depending on how we choose to implement the creation of the itinerary, event objects could be created that correspond with the above fields. A date field has been included to allow for filtering of these objects by their dates, so they will be grouped with events on the same day. When the user books an event, an object can be generated and passed into the itinerary event for displaying.

Functions would have to be created in order to modify any received input, such as date and time, into a uniform format that is suitable display.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] - My code follows the code style of this project.
[ ] - My change requires a change to the documentation.
[ ] - I have updated the documentation accordingly.
[ ] - I have read the wireframe document.
[ ] - I have added tests to cover my changes.

vercel[bot] commented 10 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bay-view	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 3, 2023 9:57pm

heyitsmass commented 10 months ago

Please run the ./start -t command with the updated start script before creating a pull request to validate the build can deploy

cpilande commented 10 months ago

@heyitsmass It says that "bayview-development exited with code 0". Is that good to go?

heyitsmass commented 10 months ago

@heyitsmass It says that "bayview-development exited with code 0". Is that good to go?

Correct, it should pass the

bayview-development | Linting and checking validity of types ...

stage and exit with

bayview-development exited with code 0

heyitsmass / BayView