This repository has been archived by the owner on Dec 3, 2022. It is now read-only.
Include v5 patching for users converting from v4 to v5? #65
Comments
|
Hi
Sorry can you explain, I'm not sure to understand.
If we can make it easier to migrate hooks from v4 to v5, we should
probably, but don't know how
Le mar. 24 mars 2020 à 20:49, Alex Chin <notifications@github.com> a écrit :
… Would it be an idea to import useNavigation from
***@***.***/native';`` and use that if the user has
react-navigation v5 installed? I'm in the process of upgrading from v4 to
v5 and of course lots of my screens are broken.
It might be a silly idea?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#65>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFW6PQRIGB7JKAMREQMXT3RJEFEXANCNFSM4LS6EMFA>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would it be an idea to import
useNavigationfrom `'@react-navigation/native';`` and use that if the user has react-navigation v5 installed? I'm in the process of upgrading from v4 to v5 and of course lots of my screens are broken.It might be a silly idea?
The text was updated successfully, but these errors were encountered: