3 Comments

  1. Jake Hawkes

    Isn’t Frontify setting the state on all the objects from the WP API, which is still incomplete? I sure do hear many developers complain that managing state and viewing explicit data structures created by state managers is difficult? Seems like one of the major benefits of GraphQL is it is super easy to see, define, and ship data structures (GraphiQL). Any thoughts?

    Report

    • Michal Czaplinski

      Hi Jake! Michal from the Frontity dev team here :)

      GraphQL is a great technology and we’re all fans here at Frontity. It makes fetching arbitrarily complex data a breeze. But GraphQL is only part of the story, it will only help you to fetch your data. In order to actually “manage” it (e.g. update the state on the client only, decide when to re-render your components when something changes) you need to go further and use a state manager.

      The Apollo team is trying to promote using graphQL-like API for client state management with apollo-link-state: https://www.apollographql.com/docs/link/links/state/

      We took a different route provide an opinionated state manager which we think is best-in-class. It combines the best parts of the immutable (like redux) and mutable (like MobX) approach to state management: The ease of the mutable API and the observability and traceability of the immutable approach.

      We are also working on creating a devtool which will be very similar to the redux-devtools which will allow you to track the changes to state, view each dispatched action, etc. This provides many of the same benefits as GraphiQL, but without having to buy into learning graphQL!

      Report

  2. Peter Shaw

    Service workers, caching and faster broadband make front end frameworks redundant. A million pounds for dead end tech. Some people have more money than sense.

    Report

Comments are closed.

%d bloggers like this: