[PLA-2094] Fixes email validation on linux

[leonardocustodio]

PR Type

Bug fix

---

Description

• Updated email validation logic in start.sh.

• Replaced regex validation with a case pattern check.

• Improved user feedback for invalid email input.

---

Changes walkthrough 📝

	Relevant files
Bug fix	start.sh Refactor email validation logic in `start.sh`                        start.sh Replaced regex-based email validation with a case pattern check. Enhanced user feedback for invalid email inputs. Simplified validation logic for better maintainability. +7/-4

---

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

[github-actions]

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 Validation Logic Change The email validation logic has been replaced with a case pattern check. Ensure that the new pattern *@?*.?* is robust enough to handle common email formats and edge cases. case $NOTIFICATION_EMAIL in *@?*.?*) ;; # Valid pattern *) echo "The email address you provided is not valid. Please try again." read_email ;; esac

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add termination condition to recursion Ensure the read_email function handles invalid email inputs robustly by adding a termination condition to prevent infinite recursion in case the user repeatedly provides invalid email addresses. start.sh [58-64] case $NOTIFICATION_EMAIL in *@?*.?*) ;; # Valid pattern *) echo "The email address you provided is not valid. Please try again." + if [ "$RETRY_COUNT" -ge 3 ]; then + echo "Too many invalid attempts. Exiting." + return + fi + RETRY_COUNT=$((RETRY_COUNT + 1)) read_email ;; esac Suggestion importance[1-10]: 9 Why: The suggestion addresses a critical issue of potential infinite recursion in the read_email function by introducing a termination condition after a certain number of invalid attempts. This improves the robustness and reliability of the script, preventing it from getting stuck in an endless loop due to user error. The implementation is accurate and directly relevant to the PR changes.	9