'Add __private__ field to EnumValueDefinition struct'
#2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix deprecation warnings in Elixir 1.11
…ne-description-in-sdl Escape single-lined description in SDL
…rm-populate Fix compilation bug with persistent_term backend
…l_generation Fix SDL generation for interfaces
This reverts commit 5b4f198.
Move to GitHub actions
Allow NimbleParsec ~> 1.0
…oc_fixes Doc fixes
Bump version 1.5.4
…bsinthe-graphql#1125) * Invert the phoenix installation instructions. Add the instructions for current versions of Phoenix as the default, and then explain how to use in older versions rather than the other way around. * Restore fence syntax
…1080 Validate object/interfaces implement all transitive interfaces
…1128) Absinthe's telemetry events includes `id` metadata, as means to correlate start/stop/exception events. Telemetry defines a `telemetry_span_context` for this same reasons. This patch publishes the same `id` value as both keys, sowe maintain backwards compatibility as well keep adherent to conventions, for tools that rely on that - like OpenTelemetry. The `telemetry_span_context` is generated using `:erlang.make_ref/0`. Given typespecs describe as `term`, should be safe to use the same value as `id`.
…ve_type_only_object Prevent key :is_type_of not found error on interfaces
* Add unique field names validation Fixes absinthe-graphql#1133 Also fixes absinthe-graphql#1049 as the schema's won't compile anymore, so the warning no longer happens * Optimize duplicate?/3 check * Add changelog entry
…the-graphql#1142) The InputOutputTypesCorrectlyPlaced phase did not work for SDL schema's since it would unwrap a TypeReference, which yields the TypeReference and not the type atom. The subsequent lookup in the schema types would therefore fail, as it expects atoms not typereferences, and it would not add errors. It now correctly fetches the atom type identifier, though in a bit of a roundabout way.
* Add TypeReference.name/1 to get graphql representation Necessary to get the name of the type when the underlying type may not exist in the schema and therefore `Absinthe.Type.name/1` won't work. * Match spec on allowed variable usage spec: https://spec.graphql.org/October2021/#sec-All-Variable-Usages-are-Allowed fixes absinthe-graphql#1134 Several cases did not return errors * when the location type was non nullable and the variable nullable * when the location type was a list and the variable wasn't Some cases are allowed: * contravariant, when the location type is nullable and the variable non-nullable * the the argument is non-nullable but either the variable or argument has a default value * Fix invalid documents in tests * Remove obsolete directive tests With the changes on allowed variable usage they would only test whether the directive variable in the operation was present. This is covered elsewhere. * Add changelog entry for absinthe-graphql#1141 * Format according to elixir 1.10
…#1140) * Make invalid scope errors more useful * Extract deprecated directive fields into separate phase This change was necessary to to implement macro-based directive handling. Because these fields are deprecated, they would use the new `deprecated` directive. This directive definition is taken from the prototype schema. However, during compilation of the prototype schema it would also invoke the introspection builtins with 'deprecated' directive, which is not yet available. This new phase extracts the deprecated fields, thus allowing the prototype phase to skip it in its schema pipeline to avoid the problem. In Absinthe 2.0 the entire phase can be removed but as of now it's a backwards incompatible change. * Add directive/1,2 to notation to apply type system directives This also handles deprecation at the directive level, so it works similar to SDL schema's. * Update lib/absinthe/schema/notation.ex Co-authored-by: Yu Matsuzawa <ymtszw@gmail.com> Co-authored-by: Yu Matsuzawa <ymtszw@gmail.com>
* Add failing test cases for wrapped unknown types * Fix check unknown wrapped types * Add Did you mean? suggestions for unknown types * Add changelog entry for absinthe-graphql#1138 Co-authored-by: Ben Wilson <benwilson512@gmail.com>
* Update changelog * Update docs * Update ex_doc
…raphql#1146) * Update non_null.ex * Update lib/absinthe/type/non_null.ex Co-authored-by: Ben Wilson <benwilson512@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
--