shuding/nextra

bring back feedback.useLink

Open

#4,075 opened on Jan 26, 2025

View on GitHub
 (1 comment) (1 reaction) (0 assignees)TypeScript (1,413 forks)user submission
enhancementhelp wanted

Repository metrics

Stars
 (13,807 stars)
PR merge metrics
 (Avg merge 6d 16h) (3 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

this was removed in v4 for no apparent reason and there's no way to configure it anymore

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

same as v3

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

Research direction
Investigate the git history to find when and why feedback.useLink was removed in v4. Look at the v3 implementation of feedback component and find the relevant configuration. Determine how to reintroduce the option, possibly restoring the old logic or creating a new implementation that allows specifying a custom link for feedback. Check for any discussions in issues or pull requests about this feature.
Tech stack
typescriptnextjsreact
Domain
frontenddocumentation
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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
familiarity with Nextraunderstanding of Reactbasic knowledge of configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60