These are chat archives for jdubray/sam
Hi @jdubray ...I am driving out a react-native application using their
NavigationExperimental using SAM. One thing I am wresting is the factoring of code implementing a 'navigator' history component for handling screen transitions, etc. I get that the 'State' portion should be a computation of current application state making it itself essentially 'stateless'. But a history/navigator component inherently requires being stateful...like keeping track where the user is inside a navigator sequence.
My gut tells me this:
Does this seem like the right direction to go?