chore: Clearing email field after waitlisting the user email

[bansal-harsh-2504]

User description

Description

Now if the user email gets waitlisted then the email field will be cleared for better user experience.

Related to #474

Mentions

@rajdip-b

Developer's checklist

• My PR follows the style guidelines of this project
• I have performed a self-check on my work

If changes are made in the code:

• I have followed the coding guidelines
• My changes in code generate no new warnings

Documentation Update

• No documentation changes are required.

---

PR Type

enhancement

---

Description

• Fixed a typo in the error message displayed when the email field is empty.
• Enhanced user experience by clearing the email input field after the email is successfully waitlisted.

---

Changes walkthrough 📝

	Relevant files
Enhancement	index.tsx Improve user experience by clearing email field post-waitlisting apps/web/src/components/hero/index.tsx Fixed a typo in the error message for empty email input. Added functionality to clear the email field after successful waitlisting. +3/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The catch block for the fetch request only logs the error to the console. Consider implementing proper error handling and user feedback. User Feedback After clearing the email field on successful waitlisting, consider providing a success message to the user for better UX.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Enhance user feedback by displaying success and error messages after waitlist submission attempts Consider adding a success message to inform the user that their email has been successfully added to the waitlist. apps/web/src/components/hero/index.tsx [38-47] try { await fetch(`${url}&EMAIL=${email}`, { mode: 'no-cors' }) setEmail(''); - + toast.success('Successfully added to the waitlist!'); } catch (error) { - // eslint-disable-next-line no-console -- chill - console.error(error) + console.error('Failed to add email to waitlist:', error) + toast.error('Failed to add email to waitlist. Please try again.'); } Apply this suggestion Suggestion importance[1-10]: 8 Why: Adding user feedback through success and error messages significantly improves the user experience by providing clear communication about the outcome of their actions. This enhancement is valuable for usability.	8
Best practice	Use a more descriptive variable name for the API endpoint URL to improve code readability and maintainability Consider using a more descriptive variable name for the API endpoint URL, such as waitlistApiUrl or emailSubmissionUrl, instead of the generic url. apps/web/src/components/hero/index.tsx [39-41] -await fetch(`${url}&EMAIL=${email}`, { +await fetch(`${waitlistApiUrl}&EMAIL=${email}`, { mode: 'no-cors' }) Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion to use a more descriptive variable name for the API endpoint URL enhances code readability and maintainability, making it clearer what the variable represents. This is a good practice, although it does not address a critical issue.	7
Possible issue	Improve error handling to account for potential issues when clearing the email field after a successful submission Consider adding error handling for the case when the email is successfully added to the waitlist but clearing the email field fails. apps/web/src/components/hero/index.tsx [38-47] try { await fetch(`${url}&EMAIL=${email}`, { mode: 'no-cors' }) setEmail(''); - } catch (error) { - // eslint-disable-next-line no-console -- chill - console.error(error) + console.error('Failed to add email to waitlist:', error) } +if (email !== '') { + console.warn('Failed to clear email field after successful submission') +} + Apply this suggestion Suggestion importance[1-10]: 6 Why: The suggestion adds additional error handling for the scenario where clearing the email field might fail. This improves robustness but is not critical since the failure to clear the field is unlikely to cause significant issues.	6

💡 Need additional feedback ? start a PR chat

[rajdip-b]

LGTM

[rajdip-b]

@kriptonian1 can you review and merge this? Just make sure the original issue doesn't get closed

[bansal-harsh-2504]

@kriptonian1 @rajdip-b Can you please add hacktoberfest label before merging?

[rajdip-b]

for sure

[rajdip-b]

🎉 This PR is included in version 2.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀