I blog occasionally and poorly, but this is what I’ve got.
This is a quick follow up to my prior post about strictly using Python instead of the CLI with AWS Cloud Development Kit. In…
AWS went GA with the Cloud Development Kit (CDK) today. The TLDR is that this a way to really build your infrastructure as code…
A quick a dirty example of how a dictionary could be used modify Graphene ObjectType field definitions without restarting the engine.
I also wrote a series on using GraphQL in Python
Rather than rehashing the virtues of GraphQL or doing another JS demo, I’d like to dive into a quick start around building an engine using Graphene – a Python implementation of the GraphQL spec.
In GraphQL, an ObjectType is a basic primitive that represents a “thing you can query.” So let’s implement our first `ObjectType`.
On the surface, there wasn’t anything too complicated in declaring the `ObjectType `, but how Graphene would know how to assign values to the `Fields`?
While a “field” in GraphQL is a generic for several things, it is also a mapping device that makes the graph possible. Without a Field, the ObjectType and the resolver remain unbounded from each other.
In GraphQL, a schema is a root level type that is meant to collect and expose all the functionality available through that node. It’s also at this point that I begin to slide away from needing to think strictly about Python and one type and start thinking in terms of graphs.