[docs] Remove outdated bridge and null state references from AppState docs#4985
[docs] Remove outdated bridge and null state references from AppState docs#4985dr-thca wants to merge 1 commit intofacebook:mainfrom
Conversation
|
Hi @dr-thca! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
be6f2b4 to
90bede8
Compare
Summary
AppState.currentStatedocumentationcurrentStatebeingnullat launch, which is no longer the case with the new architectureContext
Fixes #4689
Since React Native 0.76, the new architecture (TurboModules) is the default.
AppState.currentStateis now populated synchronously viagetConstants()during module construction, so it is nevernullwhen user code accesses it. The old documentation referenced the "bridge" and a transientnullstate that no longer applies.The TypeScript types already declare
currentStateas non-nullable (AppStateStatus), so this change aligns the prose with the types and the runtime behavior.Changes
Two sentences updated across 8 files (
docs/appstate.md+ versioned docs for 0.77-0.83):currentStatewill be null at launch whileAppStateretrieves it over the bridge."