elm-lang.org VS elm-graphql

That talk is old and the experience of people with extensible records has been a mixed bag of good and bad experiences. Evan ended up removing the section about extensible records from the official documentation. Be mindful of this findings when contemplating the use of extensible records.

Once I could quickly make calls against a server, and see the raw responses were matching up to my expectations, I moved to finding an Elm equivalent. Two years ago or so, Dillon had his GraphQL library and marketed it well.

The elm-graphql library enables code generation. This enables us to extend the “fearless refactoring” across the entire stack. As we build, learn, and eventually change our domain model from those learning’s, we can regenerate the front-end code needed, and the compiler lets us know what to modify (I still haven’t found something this powerful for ReScript yet).

I've managed to run the example from dillonkearns examples at master, however it is using a strange version of Swapi/Object with CustomScalarCodecs instead of ScalarCodecs generated by his code generation utility. I'm new to Elm, so costed me some time to make the Starwars.elm file work with properly generated classes, since even Id types in the repo example are not matching the generated types (Int vs String).