redux sagas unnecessary?

[headwinds]

I went through your awesome example and learned quite a lot.

I see that you actually decided not to use redux sagas though - did you do this because it's not necessary once you have Apollo setup?

This Apollo article seems to confirm that redux-sagas may not be needed but if we wanted to talk to a API that wasn't using GraphQL wouldn't one still need to use a thunk or a saga to make that call?

[srghma]

@headwinds
sorry for late response, didn't receive email about your comments

I have slightly abandoned this project lately

Sagas ... I think something like this is necessary (how I'll make auth module without them?), but I want to use redux-logic (application structure I saw when learned ngrx, awesome article from creator)

Also, I want to try https://github.com/nozzle/react-static, because next.js stopped in development

Also seems like relay is better because it doesn't make me do low-level error-prone things

Also, containers structure will be like

\presentations
   \default.tsx
   \error.tsx
   \no-data.tsx
\feature.ts - joins presentations with recompose (branches), adds logic by wrapping in per-component redux store (withState) 
\apollo/relay/dunno.ts
\index.ts - wraps feature.ts in apollo and main redux store