UI: Enhance Error Message Specificity in User Invite Modal

[zihanKuang]

Notes for Reviewers

This PR fixes #1050

Reason for Changes

The primary goal is to improve the user experience by providing more specific and actionable feedback when an invitation fails due to common, understandable reasons. This allows users to better diagnose the issue.

By whitelisting specific messages for detailed display, I avoid exposing end-users to potentially confusing or overly technical error messages.

[leecalcote]

Create new error codes in the respective handlers.

[zihanKuang]

Hi @FaheemOnHub,

I've just pushed the latest updates to my backend PR: https://github.com/layer5io/meshery-cloud/pull/3527. Could you please take a look and let me know if any further modifications are needed?

Separately, regarding my frontend PR, could you advise if this should now be closed, or if it still requires further updates or work from my side?😊

Thanks!

[FaheemOnHub]

Hi @FaheemOnHub,

I've just pushed the latest updates to my backend PR: layer5io/meshery-cloud#3527. Could you please take a look and let me know if any further modifications are needed?

Separately, regarding my frontend PR, could you advise if this should now be closed, or if it still requires further updates or work from my side?😊

Thanks!

as currently we don't have notification center, we could just display the short description in err.

[FaheemOnHub]

is it necessary to hardcode, we can directly display the error message 🤔

[zihanKuang]

Hi @FaheemOnHub, thanks for the feedback!

You're right, but the backend can send various error messages. My thinking was to specifically check for error.data.code === INVITE_EXISTING_USER_ERROR_CODE so we can provide user-friendly guidance for that particular scenario. For other potential errors from this endpoint, I fall back to a more general message. So I use hardcode to identify.