Django React/Redux Base Project

Post by hiram112 » Thu, Oct 27, 2016, 5:25 PM UTC

nsomaru wrote: post #36

ecesena wrote: post #19

Earlier quoted context omitted.

If your project is small enough you can scrape it and generate all pages. You need a server only in development but then you can host it statically (and for free, e.g. on github). Check out hasgluten.com for an example, code here (pretty old version of react though): https://github.com/hasgluten/hasgluten

That's useful, thanks. The case I was interested in is where you'd like to have Django server-side-render the first request based on url, and then have react handle the rest via react-router and apis ala django-rest-framework. As a backend dev who got by with jquery soup and 0 frontend build tools before (use django bundling tools), even starting to approach the React ecosystem is a little daunting.

Post by cheapsteak » Thu, Oct 27, 2016, 5:34 PM UTC

ng12 wrote: post #32

gitaarik wrote: post #13

So for people who think they need Redux, first read "You Might Not Need Redux" [0] by Dan Abramov himself, creator of Redux. Then also I would recommend MobX [1] over Redux, it's easier to get started and in my opinion easier and better in general. [0] https://medium.com/@dan_abramov/you-might-not-need-redux-be4... [1] https://github.com/mobxjs/mobx

Correct me if I'm misunderstanding, but one thing that worries me about MobX is that it seems leakier than Redux. Something that I really, really care about is that a well-architected React application should hardly care what the data layer is. The bulk of the application is comprised of dumb/presenter components and only the handful of container components know anything about Redux. Things like this (from the docs)…

    const TodoView = ({title, isFinished, onClick}) => (
        
            {title}
        
      )

    const TodoViewContainer = observer({todo} => (
         todo.finished = !todo.finished}
        />
      ))

Post by paol » Thu, Oct 27, 2016, 5:44 PM UTC

gitaarik wrote: post #13

So for people who think they need Redux, first read "You Might Not Need Redux" [0] by Dan Abramov himself, creator of Redux. Then also I would recommend MobX [1] over Redux, it's easier to get started and in my opinion easier and better in general. [0] https://medium.com/@dan_abramov/you-might-not-need-redux-be4... [1] https://github.com/mobxjs/mobx

Post by blamarvt » Thu, Oct 27, 2016, 5:53 PM UTC

robohamburger wrote: post #29

I feel like the best way to do this is to just use cornice or DRF then use js scaffolding that is completely unaware of your backend. No need to join them at the hip like this, except maybe for the token based auth?

Post by ng12 » Thu, Oct 27, 2016, 5:59 PM UTC

cheapsteak wrote: post #44

ng12 wrote: post #32

Earlier quoted context omitted.

Correct me if I'm misunderstanding, but one thing that worries me about MobX is that it seems leakier than Redux. Something that I really, really care about is that a well-architected React application should hardly care what the data layer is. The bulk of the application is comprised of dumb/presenter components and only the handful of container components know anything about Redux. Things like this (from the docs)…

You can easily maintain the abstraction of dumb components if you wish to: const TodoView = ({title, isFinished, onClick}) => ( {title} ) const TodoViewContainer = observer({todo} => ( todo.finished = !todo.finished} /> )) But how often are you changing your app's data layer? Is the tradeoff _always_ worth it? Mobx allows you to be as pragmatic or dogmatic as you choose to be