medium10 pts · first answer countscross-platform-mobilereact-nativenavigation

Passing a callback as a route param

A screen is opened with `navigate('Edit', { onSave: () => refresh() })` and React Navigation warns about non-serializable values. Why does it matter?

A.Functions in params make the app crash on every Android deviceB.The callback is called twice on every render of the screenC.Params can only hold strings, so the number props are lostD.State persistence and deep links cannot restore functions in params

Discussion 0

Join free to post in the discussion.

Passing a callback as a route param

Discussion 0

Related questions