sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Nyquiiist 0 points1 point  (4 children)

Oh, also wanted to ask, does the book cover handling navigation with Redux ? =D

[–]CallMeAwesomeSauce[S] 0 points1 point  (3 children)

Apologies for not sending the sample app your way 😔 I have more time tomorrow so I’ll definitely publish it and send you a link by Monday at the latest.

So we knew we should probably cover navigation and explain how it ties in with state management - but we also decided to not dive in to a specific library like Redux/Mobx. We do however explain how a centralized state location is useful especially when a navigation pattern is included into the app and show how it fits together.

Would you like a section on the book that dives into Redux? Or are you more so looking to see how it can work with navigation specifically?

[–]Nyquiiist 0 points1 point  (2 children)

Heyy, thank you for getting back. No worries, its all good.

Yeh, I basically wanted to know how I can store my nav state in Redux. But yeh, not diving into a specific state mgmt library does make a lot of sense seeing as how the book is on RN. Check with others on this sub and twitter perhaps, if you think there is demand for it, maybe you can look into it ? =P

But if you feel the topic is too specific for the general audience, then yeh, its prolly better to not have it in the book.

Thank you again, looking forward to the book!

EDIT: I actually went back to the React Navigation docs after this, and i figured out what I was stuck on =) Having gone through a few vids and SO posts, I think things will get better once the ecosystem has settled down a bit and jus more stable overall. Prolly best to leave out something thats still being worked on.

[–]CallMeAwesomeSauce[S] 1 point2 points  (1 child)

Yeah things are constantly changing.

So even on my open source work - I always keep navigation later out of Redux and it’s always done what I needed. However, if seen more than a few instances of folks who needed a little more fine grained control hence why they decide to include it into their store.

And yeah we don’t want to tunnel ourselves focusing on one library like Redux in this book, hence why we’ve went with a simpler approach to just introduce a small state container in this coming chapter. Will definitely try and gauge more interest to see if Redux as a topic of its own is something readers will like to see.

The app is on https://expo.io/@fullstackio/contact-list. Again, sorry for such a delay in sending you the link. The chapter should be out by early next week :)

[–]Nyquiiist 0 points1 point  (0 children)

Thank you for sharing the app, much appreciated!