You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an error occurs during the submission process, it will be caught by the generic catch block, but the error message will not be displayed to the user.
👟 Reproduction steps
Ensure the createJob API endpoint or the uploadFileAction function is mocked or simulated to return an error response (e.g., 500 Internal Server Error
Click the submit button to trigger the handleFormSubmit function.
Observe the console or error logs.
👍 Expected behavior
The error should be caught and displayed to the user through the toast notification system.
👎 Actual Behavior with Screenshots
The error is caught by the generic catch block, but the error message is not displayed to the user.The error is logged to the console, but no user-friendly error message is shown.
OS name
MacOS
browser name
Chrome
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
If an error occurs during the submission process, it will be caught by the generic catch block, but the error message will not be displayed to the user.
👟 Reproduction steps
👍 Expected behavior
The error should be caught and displayed to the user through the toast notification system.
👎 Actual Behavior with Screenshots
The error is caught by the generic catch block, but the error message is not displayed to the user.The error is logged to the console, but no user-friendly error message is shown.
OS name
MacOS
browser name
Chrome
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: