refly-ai/refly

Provide Clear Error Message When Failing to Access Links in Questions

Open

#747 opened on Apr 16, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)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.

Contributor guide

Tech stack
typescript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of frontend error handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
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.