microsoft / microsoft/react-native-windows
Override tool needs better error messaging/instructions
Open
Nobody has claimed this yet.
Deforking
enhancement
Only Affects Internal Development
Quick Task
Workstream: Releases and Integrations
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
@NickGerleman sez: Expected file path should be relative to "react-native", so you just need the ReactCommon part. We should have a better error message there though...
Contributor guide
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 by reproducing the Override tool error with the path shown in the issue image, then trace where the expected relative path is validated. Done means the failure explains that paths are relative to "react-native" and identifies the ReactCommon portion; verify the updated message with the tool's available checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100