microsoft / microsoft/react-native-windows
Make react-native-windows-init oblivious to project generation flags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
CLI Options for project generation can vary between different versions of RNW as new features/flavors are added or removed. Each of these currently need to be added to react-native-windows-init, which needs to support every version of RNW.
We should try to make react-native-windows-init oblivious to project generation options and expose a mechanism to declare them on the project generation side of the boundary.
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 reading the react-native-windows-init entry point and the project-generation side of the boundary. Trace how generation flags are currently passed and how RNW versions expose them. Done means react-native-windows-init no longer needs version-specific project-generation options while the generation side can declare those options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- cli, developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100