Vince Foley

Currently, this plugin will crash if the Elixir app is structured as an umbrella app. In an umbrella app, the `_build` directory is nested inside the top level app, not...

This PR simply adds elixir to the set of fenced languages for syntax highlighting! Thanks!!

Add extend to macro defined schemas

5

This PR introduces an `extend` macro that behaves as the "extend" concept in the GraphQL spec: * https://graphql.github.io/graphql-spec/draft/#sec-Object-Extensions We can extend `object`, `input_object`, `enum`, `union`, and `interface`. The GraphQL spec...

Make persistent_term schema provider the default

1

* Make persistent_term schema provider the default, hint users to add `Absinthe.Schema` to their supervision tree * Erlang 21.2 required, provide helpful error message if `persistent_term` is not present

Generate Blueprint structs from introspection query

1

Take the result of an introspection query and generate `Blueprint` structs. From that point, we can do anything with those structs, including rendering `SDL` or generating a schema module. Split...

Support TypeSystem Directives

4

The latest GraphQL spec includes `TypeSystemDirective` (directives that annotate the type system) alongside the `ExecutableDirective` (directives that annotate query execution) https://spec.graphql.org/draft/#TypeSystemDirectiveLocation Absinthe has full support for `ExecutableDirective`s, but only partial...

There's a new directive that will soon be in the spec for Custom Scalars called `specifiedBy` https://github.com/graphql/graphql-spec/pull/649 Example: ```graphql scalar UUID @specifiedBy(url: "https://tools.ietf.org/html/rfc4122") scalar URL @specifiedBy(url: "https://tools.ietf.org/html/rfc3986") ```

> We should do a pass in the absinthe code base and eliminate all bare atom identifiers within blueprints and standardize on `%TypeReference.Name{} | %TypeReference.Identifier{}` Noted in https://github.com/absinthe-graphql/absinthe/pull/780/files#r322457359 This will...

Instrumentation hooks for trace context propagation

17

I'm interested in seeing `telemetry` extended with an API to enable an additional type of instrumentation - the mutation of an outbound request / query with Distributed Trace context information....

Allow multiple clients

2

I've adapted the `Client` to be able to start multiple `GenServer`s. I didn't want to change the behavior of any of the other `start_link` functions, so there's a new function...