Slaying a UI Antipattern in React – JavaScript Inside – Medium

How to solve an UI anti pattern with React ? A great post by @sharifsbeat  #ReactJS

  • Setting the items to null instead of an empty array creates even more problems so that won’t help either.Stefan Oestreicher, Slaying a UI Antipattern in FantasylandSo we have to manually keep track of the current data status, making sure we don’t forget to set the correct loading, error and data…
  • Forgetting to keep the state in sync leads to a false representation in the UI.In Slaying a UI Antipattern in Fantasyland we are represented with a different way to think about the problem:type RemoteData e a = NotAsked | Loading | Failure e | Success aWe might have different states…
  • By modelling all possible states, we can resort to using daggy f.e., which enables us to handle the possible outcomes.const RemoteData = daggy.taggedSum({ NotAsked: [], Loading: [], Failure: [‘error’], Success: [‘items’],})// in our constructorthis.state = { items: RemoteData.NotAsked }(* Taken from Slaying a UI Antipattern in Fantasyland)By now we should…
  • Loader /What if we could take all these ideas and wrap them inside a React component, which takes care of all of this, without having to manually take care of the low level stuff.Michael Jackson wrote about the render-props concept in his Use a Render Prop!
  • Now we don’t have to think about if the UI is representing the proper state, all we need to do is tell Loader / what we want to see if the component is loading, has an error and has any data.Now that we have an idea of how Loader should…

The following write-up is based on Stefan Oestreichers blog post Slaying a UI Antipattern in Fantasyland which was originally influenced by Kris Jenkins excellent how Elm slays a UI antipattern. Just…
Continue reading “Slaying a UI Antipattern in React – JavaScript Inside – Medium”

Slaying a UI Antipattern in React – JavaScript Inside – Medium

  • Setting the items to null instead of an empty array creates even more problems so that won’t help either.Stefan Oestreicher, Slaying a UI Antipattern in FantasylandSo we have to manually keep track of the current data status, making sure we don’t forget to set the correct loading, error and data…
  • Forgetting to keep the state in sync leads to a false representation in the UI.In Slaying a UI Antipattern in Fantasyland we are represented with a different way to think about the problem:type RemoteData e a = NotAsked | Loading | Failure e | Success aWe might have different states…
  • By modelling all possible states, we can resort to using daggy f.e., which enables us to handle the possible outcomes.const RemoteData = daggy.taggedSum({ NotAsked: [], Loading: [], Failure: [‘error’], Success: [‘items’],})// in our constructorthis.state = { items: RemoteData.NotAsked }(* Taken from Slaying a UI Antipattern in Fantasyland)By now we should…
  • Loader /What if we could take all these ideas and wrap them inside a React component, which takes care of all of this, without having to manually take care of the low level stuff.Michael Jackson wrote about the render-props concept in his Use a Render Prop!
  • Now we don’t have to think about if the UI is representing the proper state, all we need to do is tell Loader / what we want to see if the component is loading, has an error and has any data.Now that we have an idea of how Loader should…

The following write-up is based on Stefan Oestreichers blog post Slaying a UI Antipattern in Fantasyland which was originally influenced by Kris Jenkins excellent how Elm slays a UI antipattern. Just…
Continue reading “Slaying a UI Antipattern in React – JavaScript Inside – Medium”

Super excited to have @ryanflorence speaking about #react router at the next ReactNYC, meetup Aug 15 #reactjs

  • In this meetup we have two special guests: James Baxley from South Carolina (working on Apollo for Meteor) and Ryan Florence from Seattle (co-creator of react-router).
  • By the way, Ryan Florence and Michael Jackson have React workshops for beginners and experienced developers on 16, 17 and 18 of August.
  • In this talk I will propose some different approaches to hiring, recruiting, and managing developers by borrowing best practices from the tattoo industry.
  • Easy Server Side Rendering with GraphQL

    James Baxley

    React has unified how teams think about application development.

  • Let’s talk: [masked]

    At Enigma, we believe in the power of data to tackle tough challenges.

In this meetup we have two special guests: James Baxley from South Carolina (working on Apollo for Meteor) and Ryan Florence from Seattle (co-creator of re
Continue reading “Super excited to have @ryanflorence speaking about #react router at the next ReactNYC, meetup Aug 15
#reactjs”

React Router v4, RxJS with React/Redux, React Components

  • Learn about React Router V4, RxJS with React and Redux, React Components and more at this action packed meetup hosted by Modern Web !
  • 7:35 – 8:05 Reusable React Components with Mars Jullian
  • Topic: RxJS Makes React + Redux Amazing
  • Topics: web components, ember, angular, react, polymer, async programming, libraries such as bacon.js, rxjs, scalability, native promises & performance, es6/es7 iterators and generators, reactive extensions, object oriented design in es6, traits.js, design patterns and more.
  • 6:45 – 7:15 React Router v4 with Michael Jackson

Read the full article, click here.


@burgessdryan: “Excited for @modernweb_ meetup in Sept. A full night of #ReactJS @mjackson @marsjosephine @_jayphelps and @sprjrx”


Learn about React Router V4, RxJS with React and Redux, React Components and more at this action packed meetup hosted by Modern Web! Make sure to RSVP at http://www.meetup.com/modernweb/events/2322441


React Router v4, RxJS with React/Redux, React Components