microsoft / microsoft/react-native-windows
Autolinking should bail if there are two projects with the same name
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
E.g.: @react-native-community/clipboard and @react-native-clipboard/clipboard
SLN files must not have two projects with the same name
Autolinking will happily write the two dependencies into the SLN file but msbuild will refuse to build the resulting solution file
Autolinking should instead fail with an appropriate error message
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 tracing the Windows autolinking path that writes SLN files, using the duplicate project names described in the issue as the reproduction. Verify how @react-native-community/clipboard and @react-native-clipboard/clipboard are handled, then make completion mean that autolinking stops with an appropriate error before producing an invalid solution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100