3 ms·

I hate using componentWillReceiveProps but always end up doing so because it seems to be the easiest with redux. The static function replacement seems very natu

by ixtli 9y ago

I hate using componentWillReceiveProps but always end up doing so because it seems to be the easiest with redux. The static function replacement seems very natural.

pknopf 9y ago
I'm not shilling, but this is something I definitely don't miss using Mobx. edit: Ooops, I thought the commenter was referring to shouldcomponentupdate. Sorry for the confusion, please downvote this out of the discussion!
- nawgszy 9y ago
  Is it possible to shill for an open source library which, as far as I can tell, has no monetization path?
  - pknopf 9y ago
    If you are going to get technical, ask James Newton-King what Json.NET did to his career trajectory. It definitely has an intangible value.
- spicyj 9y ago
  What is the alternative? For when you have a stateful component that "reacts" to new parameters.
  - pknopf 9y ago
    Mobx uses observables to monitor what properties you read and collections you enumerate during your render method. It then uses that information to implement shouldComponentUpdate for you. Each render call refreshes the data use by shouldComponentUpdate. It gives you 100% percise updating of react components based on state, for free.
    - spicyj 9y ago
      Were we not talking about componentWillReceiveProps, not shouldComponentUpdate?
      - pknopf 9y ago
        Shoot, my bad. Sorry for the confusion. That is a common common complaint with redux, so I read into it.
        spicyj 9y ago
        No worries, I was just confused what you meant. :)