refactor: handleNewBooking #5

[Udit-takkar]

What does this PR do?

• Fixes #XXXX (GitHub issue number)
• Fixes CAL-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my changes generate no new warnings

[vercel]

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

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
cal	⬜️ Ignored (Inspect)	Visit Preview		Oct 16, 2024 6:00pm
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Oct 16, 2024 6:00pm

[graphite-app]

The function declaration syntax is incorrect. Change:

export default getEventType = async ({

to:

const getEventType = async ({

This will correctly define the function and allow it to be exported properly. Also, consider adding an explicit export statement at the end of the file if this function should be the default export.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.