Intro shows "(detected)" after a manual pick from the detection-failed picker
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
When auto-detection fails and the user picks a framework from the fallback picker, the intro row still reads Framework ✔ <name> (detected) — the one flow where detection definitively failed claims it succeeded.
The "Change framework" path suppresses the suffix via the screen's manuallySelected state; the fallback FrameworkPicker never sets it (and calls setDetectedFramework for a manual pick). src/ui/tui/screens/PostHogIntegrationIntroScreen.tsx
Noticed while testing #942 against a pub-workspace monorepo, where the workspace root is intentionally not auto-detected.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/ui/tui/screens/PostHogIntegrationIntroScreen.tsx and trace the fallback FrameworkPicker path used after auto-detection fails. Reproduce a failed detection followed by a manual framework pick; done means the intro row no longer labels that selection as detected, while the Change framework path remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100