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
Summary:
Enable users to define and return custom error pages for HTTP errors within the Chainlit framework.
Description:
Currently, when HTTP errors occur in Chainlit applications, default error pages are displayed. This feature request proposes the ability for developers to create and return their own custom error pages. This enhancement would allow for more user-friendly error handling and a consistent user experience aligned with the application's branding.
Key Features:
Custom Error Page Configuration:
Allow developers to specify custom HTML, CSS, and JavaScript for error pages.
Provide configuration options within the Chainlit settings to map specific HTTP error codes (e.g., 404, 500) to custom pages.
Template Support:
Support for templating engines (e.g., Jinja2) to dynamically render error pages with context-specific information.
Benefits:
Enhances user experience by providing informative error messages.
Allows developers to maintain consistency in design and messaging across their application.
Facilitates better error handling and debugging by allowing context-specific information to be displayed.
The text was updated successfully, but these errors were encountered:
Feature Request: Custom HTTP Error Pages
Summary:
Enable users to define and return custom error pages for HTTP errors within the Chainlit framework.
Description:
Currently, when HTTP errors occur in Chainlit applications, default error pages are displayed. This feature request proposes the ability for developers to create and return their own custom error pages. This enhancement would allow for more user-friendly error handling and a consistent user experience aligned with the application's branding.
Key Features:
Custom Error Page Configuration:
Template Support:
Benefits:
The text was updated successfully, but these errors were encountered: