Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Realease date #3

Closed
danielkv opened this issue Jan 28, 2022 · 9 comments
Closed

Realease date #3

danielkv opened this issue Jan 28, 2022 · 9 comments

Comments

@danielkv
Copy link

Is there a release date for this lib yet?

I started using the expo-next-react-navigation and I just found out from a RN radio podcast you area building this one, that is a new version of that package. So I worder if there is a release date from lauching this lib.

@nandorojo
Copy link
Owner

I'm using this lib myself now, so it's just a matter of finishing docs and examples. The code is stable to use in my experience. So I'd recommend checking out the docs so far (currently a WIP) and seeing if that's sufficient for you to get what's going on.

If not, I can't say definitively. Just depends on when I have time in the next few weeks to add docs/examples. But I'd also accept PRs for that!

If you want more context on how I arrived at this API, I recommend checking out this thread, I went in deep detail: axeldelafosse/expo-next-monorepo-example#1

@danielkv
Copy link
Author

danielkv commented Jan 31, 2022

I'm trying to understand exactly the differences between solito and expo-next-react-navigation.

I can see the API is a little different and solito seems a little simpler. I have already tested expo-next-react-navigation and I'm going to give it a try to test the new API, but if you can give me a gist of the core differences I appreciate.

The main question is: "Can I do the same things with both?"

@nandorojo
Copy link
Owner

solito is essentially a major version bump, since the API has breaking changes

@nandorojo
Copy link
Owner

yes you can do the same with both, but solito is all about sharing the mental model across platforms. the key thing is that with solito, every navigation action is triggered via URL. this is much better, since it lets your linking config become your source of truth, rather than confusing route names in nested navigators.

@danielkv
Copy link
Author

@nandorojo I'm trying to figure it out how to send params though router.push(). Do I need to parse before and generate the string before using in push method?

@nandorojo
Copy link
Owner

it's the same as next router: https://nextjs.org/docs/api-reference/next/router#routerpush

just use the pathname and query object for params. solito stringifies it into a URL for you.

@nandorojo
Copy link
Owner

I still need to add docs for that

@nandorojo
Copy link
Owner

Added docs for useRouter here: https://solito.vercel.app/usage/use-router

@danielkv
Copy link
Author

danielkv commented Feb 1, 2022

Thank you fo been so fast! I'm gonna start to convert the code today (probably). So anyway thankyou for helping the community and been so patient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants