Open tentamdin opened 11 months ago
we need to prepare the list the of possible error and how it is suppose to handle in output.
expected outputs should be the errors handled or the scope of the error handling
We need to decide error handling according to url paths available and decide a common error handling
list error 400 message mapping
RFW0101: Rethink Error Handling in Web Application
Named Concepts
Error handling: a fundamental and complex process that involves responding to and recovering from error conditions in a software application. Client side: everything in a web application that is displayed or takes place on the client's device.
Summary
Existing web applications lack a proper system for handling errors thrown by the applications. It is crucial to implement a robust error-handling system that can effectively manage various types of errors. We need to implement error handling on each different url path.
Input
Compile a comprehensive list of all types of errors encountered. Authentication Errors: User lacks proper authentication. Validation Errors:
Expected Output
Handle the expected errors are caught and gracefully handled. Authentication Errors: Redirect unauthenticated users to the login page. Validation Errors: Validate user input on the client side and provide clear error messages next to the relevant form fields. Not Found Errors (404): Customize a user-friendly 404 page. Internal Server Errors (500): Log detailed error information for developers. Display a user-friendly error message.
Eg: Error should be handle without losing the context of current page.
Expected Timeline
You need to mention the expected time line you want.
References
Below are the list of web application https://monlam.ai/ https://pecha.tools/ https://kb.iu.edu/d/bfrc