microsoft / microsoft/react-native-windows
TurboModules should be able to specify they need eager init
Open
Nobody has claimed this yet.
Area: Native Modules
enhancement
Workstream: Module Support
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
We should add a mechanism for TurboModules to specify that they want to be eagerly initialized.
Android has this as a needsEagerInit property on their TurboModule attributes. We should investigate how we want to expose this.
Once we have this, UIManager should be marked to use it. -- See #6378
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 comparing Android's needsEagerInit property on TurboModule attributes and reviewing how UIManager is represented in React Native Windows. Use the related issue #6378 for context. Done means the project has a decided mechanism for exposing eager initialization and UIManager is marked to use it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100