[MRG] Fixed the UI bug of no report generation

[huangyz0918]

User description

Closes #180

---

PR Type

Bug fix, Enhancement

---

Description

• Added error handling for when no report is found (404 status) in the fetchLatestReport function, providing a user-friendly message.
• Enhanced the UI by updating the labels and buttons for additional data sources, including links to RepX PRO for integration.
• Removed the "Save Report" button from the form to streamline the user interface.

---

Changes walkthrough 📝

	Relevant files
Enhancement	page.tsx Improved error handling and UI enhancements in report generation web/app/page.tsx Added error handling for 404 status in fetchLatestReport function. Updated labels and buttons for additional data sources with links to RepX PRO. Removed the "Save Report" button from the form. +18/-7

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Hardcoded URL The URL 'http://localhost:8000/latest_report' is hardcoded in the fetchLatestReport function. Consider using environment variables or configuration files to manage URLs, which can vary between development, testing, and production environments. Error Handling The error handling in the fetchLatestReport function throws a generic error without specifying the status code or the reason. It would be beneficial to include more specific error information to aid in debugging and user feedback.

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Replace hardcoded URL with a configurable variable Replace the hardcoded URL in the fetch request with a variable that can be configured externally. This will make the code more flexible and easier to maintain, especially in different environments (development, staging, production). web/app/page.tsx [49] -const response = await fetch('http://localhost:8000/latest_report'); +const response = await fetch(REPORT_URL); Suggestion importance[1-10]: 9 Why: Replacing the hardcoded URL with a configurable variable improves maintainability and flexibility, especially when deploying the application across different environments.	9
Possible bug	Add error handling for JSON parsing Add error handling for the JSON parsing operation when converting the response to JSON. This will prevent the application from crashing if the JSON is malformed. web/app/page.tsx [58] -const data: ReportData = await response.json(); +let data: ReportData; +try { + data = await response.json(); +} catch (error) { + console.error('Failed to parse JSON:', error); + return; +} Suggestion importance[1-10]: 8 Why: Adding error handling for JSON parsing is crucial to prevent application crashes due to malformed JSON, which enhances the robustness of the code.	8
Enhancement	Standardize button margin styling Use a consistent margin style for buttons to ensure uniformity in the user interface. web/app/page.tsx [189-194] -<Button style={{ flex: '1 1 0', margin: '2px' }} href='https://repx.app'>Zoom Meetings</Button> -<Button style={{ flex: '1 1 0', margin: '2px' }} href='https://repx.app'>Google Calendar</Button> -<Button style={{ flex: '1 1 0', margin: '2px' }} href='https://repx.app'>Slack</Button> -<Button style={{ flex: '1 1 0', margin: '2px' }} href='https://repx.app'>GitLab</Button> +<Button style={{ flex: '1 1 0', margin: '2px 2px' }} href='https://repx.app'>Zoom Meetings</Button> +<Button style={{ flex: '1 1 0', margin: '2px 2px' }} href='https://repx.app'>Google Calendar</Button> +<Button style={{ flex: '1 1 0', margin: '2px 2px' }} href='https://repx.app'>Slack</Button> +<Button style={{ flex: '1 1 0', margin: '2px 2px' }} href='https://repx.app'>GitLab</Button> Suggestion importance[1-10]: 5 Why: Standardizing button margin styling enhances the visual consistency of the user interface, although it is a minor improvement.	5