fix: |UI| admin mails unknown page call wrong api

[dreamhunter2333]

PR Type

bug fix

---

Description

• Corrected API endpoint for deleting mails in admin view

---

Changes walkthrough 📝

	Relevant files
Bug fix	MailsUnknow.vue Correct API endpoint for deleting mails                                    frontend/src/views/admin/MailsUnknow.vue Fixed the API endpoint for deleting mails from /api/mails/ to /admin/mails/ +1/-1

---

💡 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: 1 🔵⚪⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Issue Ensure that the corrected API endpoint /admin/mails/${curMailId} is the intended endpoint for deleting mails in the admin view. const deleteMail = async (curMailId) => { await api.fetch(`/admin/mails/${curMailId}`, { method: 'DELETE' }); };

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add error handling for the API call in the deleteMail function Ensure that the deleteMail function handles potential errors from the API call to avoid unhandled promise rejections. frontend/src/views/admin/MailsUnknow.vue [14] -await api.fetch(`/admin/mails/${curMailId}`, { method: 'DELETE' }); +try { + await api.fetch(`/admin/mails/${curMailId}`, { method: 'DELETE' }); +} catch (error) { + console.error('Failed to delete mail:', error); +} Suggestion importance[1-10]: 9 Why: Adding error handling to the deleteMail function is crucial to prevent unhandled promise rejections and improve the robustness of the code. This change ensures that any errors during the API call are caught and logged, enhancing the application's reliability.	9