refly-ai/refly

Provide Clear Error Message When Failing to Access Links in Questions

Open

#747 ouverte le 16 avr. 2025

Voir sur GitHub
 (0 commentaires) (0 réactions) (0 assignés)TypeScript (7 331 stars) (712 forks)user submission
enhancementgood first issue

Description

Is your feature request related to a problem? Please describe. When reading links in a question, provide a clear and specific error message if accessing the link fails. This is a request to improve the user experience by providing helpful feedback when links cannot be accessed, helping users understand why and potentially troubleshoot the issue.

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Guide contributeur

Stack technique
typescript
Domaine
frontend
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
2
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
fresh
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Basic understanding of frontend error handling
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
70
Direction de recherche
Examine the frontend code in the repository to locate components that render question content and handle link clicks. Search for files related to 'Question' or 'Link' processing. Add a try catch block around the link access logic to gracefully handle failures such as network errors or invalid URLs. Use the existing notification system (e.g., toast) to display a clear, user friendly error message explaining the failure. Review similar error handling patterns in the codebase for consistency.