microsoft / microsoft/react-native-windows
Implement new web props parity with RN core in Fabric
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Summary
RN is trying to make it easier to share code/knowledge between React web dev and React Native dev. Part of this means implementing web props in React Native.
Upstream tracking issue: https://github.com/facebook/react-native/issues/34424
Motivation
We need to maintain priority with RN core's props, though not necessarily for Paper as we lean into Fabric.
Basic Example
RN Core implemented aria accessibility props here: https://github.com/facebook/react-native/commit/720cdbc658aa0b513d106526eb81d749fa957c99
Open Questions
No response
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 with the upstream tracking issue and the React Native core commit referenced in the issue, then compare the aria accessibility props with the Windows Fabric implementation. Done means the relevant web props have parity in Fabric, with the scope distinguished from Paper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- accessibility, mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100