microsoft / microsoft/react-native-windows
Remove Fork of getNativeComponentAttributes.js
Open
@chiaramooney is already working on this.
Since Jun 9, 2025.
bug
Integration Follow-up
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Problem Description
Needed for fork getNativeComponentAttributes.js because its original file contents was producing a bunch of errors due to its usage of a deprecated comment getViewManagerConfig. I replaced these calls with the new API hasViewManagerConfig. This change should be upstreamed. The fork can be removed once the upstream PR is integrated.
Link to the integration where the error originated
https://github.com/microsoft/react-native-windows/pull/14724
Link to commit
https://github.com/facebook/react-native/compare/cee63397b...fc7385c1e
Forked files
getNativeComponentAttributes.windows.js
Upstream PR
TODO
Build Configuration
Debug
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.
Assessment
This issue has not been assessed yet.