You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-4Lines changed: 21 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,10 +191,6 @@ TODO
191
191
192
192
TODO
193
193
194
-
# TODO
195
-
196
-
- Complete examples
197
-
- Support updates with a function (like `setState(oldState => newState)`)
198
194
199
195
200
196
# FAQ
@@ -203,6 +199,27 @@ TODO
203
199
204
200
No. You can use this lib for whatever you want (including global state management) as long as it makes your life simple. For example, if you have a complex page and passing props and callbacks down becomes complicated you can create an updatable context fot that page.
205
201
202
+
### Does it work with React-Native?
203
+
204
+
Yes. Sometimes I want to share state between react-navigation screens (for example a multi-screen wizzard). That can be a replacement for `screenProps` that are not recommended to use anymore.
205
+
206
+
You can wrap your navigator with an updatable context provider for that:
0 commit comments