This fall, several people presented their work on Ruby type checkers. So let’s take a look: what’s the big deal, and what have they been up to?
You can tell Ruby on Rails to respond to changes in certain files during development.
GraphQL 1.5.0 includes a new way to define a schema: from a GraphQL definition.
One way to keep an eye on your GraphQL schema is to check the definition into source control.
graphql-ruby 1.5.0 will be released. Query execution will be ~70% faster than 1.3.0!
GraphQL Pro 1.3.0 adds support for server-defined queries via
GraphQL::Pro::Repository. In this approach, GraphQL operations are stored on the server and clients invoke them by name.
It’s possible to get IO operations running in parallel with the
graphql-ruby is almost two years old! Today, I’m adding a new element to the project,
In general, raising exceptions for control flow makes code hard to understand. However, there are other cases when an exception is the right choice.
State machines are applied to a wide variety of programming problems. I found it useful to think of a GraphQL query as a state machine.
I read that
Hash#key? was slower than
Hash# and it made me sad because, shouldn’t
Hash#key? generally require less work?