Here is a link to the book on Commanded by the author of the framework:

https://leanpub.com/buildingconduit/read

I am now onto the mutations chapter.

It seems that Decimal has changed it’s parse return. It used to be {:ok, decimal} but is now {decimal, remainder} which means that you will need the following to get Chapter 5 to build:

  scalar :decimal do
    parse fn
      %{value: value}, _ ->
        {d,_} = Decimal.parse(value)
        {:ok, d}
      _, _ ->
        :error
    end
    serialize &to_string/1
  end

The UK currently has a cost of living crisis. Inflation is going through the roof and the only think being done to influence this is to put up interest rates! The argument for this is that if credit becomes more expensive people will reduce what they are spending. Are economists so stuck in 1970’s models that they can see nothing else?

Credit card use is not rising because credit is cheap, they are rising because costs are escalating. Adding to the interest on mortgages and credit cards won’t help control this. This will drive workers to ask for larger pay rises and will fix the interest rate growth as permanent.

Fuel price rises have a massive effect across the whole supply chain. We had protests in the UK when petrol first reached 1 GBP per litre, we are now at around 1.85 GBP.

We have a leadership contest going on between two people who are denying reality and aiming for the votes of a very small electorate. Neither candidate has a sensible plan (or indeed a mandate). One wants to control inflation and the other wants to cut tax.

Still working. through the examples.

Project is at https://github.com/chriseyre2000/absinthe_demo

Currently at df7c52f

Again there is a minor difference in the error message format, and the error is a 200 not a 400.

It’s interesting to see custom modification.

Now at the end of chapter 3

Chapter 4 introduces some useful extra structure, allowing the schema to be broken down into manageable pieces.

The next step will cover unions.

This is my current VSCode settings:

{
    "files.autoSave": "afterDelay",
    "diffEditor.ignoreTrimWhitespace": false,
    "git.openDiffOnClick": false
}

It’s not much but it is a start.

Autosave is a must.
Opening the file from diff is much more sensible than assuming you want the diff.

Not got as far as I had expected on this.

Good note on this book is that the tests are immediately after the code making errors much easier to spot.

I have now looked at https://github.com/steveteuber/kubectl-graph

I was hoping for something more structured than a force directed graph. It’s a good start, but a graph starting at the exposed endpoint and listing the routes to the main service would have been more useful.

One of the first questions I ask about a new technology is can I make it play with graphviz or Neo4j

The second trick is to see if someone else has already solved it.

This time both are true:

https://github.com/steveteuber/kubectl-graph

This is a library that can export k8s setups to either graphviz or to neo4j.

I am still working through this book.

So far chapter 3 seems reasonable. The only change so far is the 200 return type for an error in a query. Previously it had been a 400.

Now at commit 9c83b41 in the repo https://github.com/chriseyre2000/absinthe_demo

We are currently at page 93 of the book (halfway through Chapter 3)