graphql-ruby-client - npm Package Versions

1.7.1 (18 Sept 2017)

Bug fixes

• Properly release changes from 1.7.0

1.7.0 (18 Sept 2017)

Breaking changes

• GraphQL::Result is the returned from GraphQL execution. #898 Schema#execute and Query#result both return a GraphQL::Result. It implements Hash-like methods to preserve compatibility.

New features

• puts ctx.backtrace prints out a GraphQL backtrace table #946

• GraphQL::Backtrace.enable wraps unhandled errors with GraphQL backtraces #946

• GraphQL::Relay::ConnectionType.bidrectional_pagination = true turns on true bi-directional pagination checks for hasNextPage/hasPreviousPage fields. This will become the default behavior in a future version. #960

• Field arguments may be accessed as methods on the args object. This is an alternative to #[] syntax which provides did-you-mean behavior instead of returning nil on a typo. #924 For example:

  # using hash syntax:
  args[:limit]    # => 10
  args[:limittt]  # => nil
  # using method syntax:
  args.limit      # => 10
  args.limittt    # => NoMethodError
  

  The old syntax is not deprecated.

• Improvements to schema filters #919

  • If a type is not referenced by anything, it's hidden
  • If a type is an abstract type, but has no visible members, it's hidden

• GraphQL::Argument.define builds re-usable arguments #948

• GraphQL::Subscriptions provides hooks for subscription platforms #672

• GraphQL::Subscriptions::ActionCableSubscriptions implements subscriptions over ActionCable #672

• More runtime values are accessible from a ctx object #923 :

  • ctx.parent returns the ctx from the parent field
  • ctx.object returns the current obj for that field
  • ctx.value returns the resolved GraphQL value for that field

  These can be used together, for example, ctx.parent.object to get the parent object.

• GraphQL::Tracing provides more hooks into gem internals for performance monitoring #917

• GraphQL::Result provides access to the original query and context after executing a query #898

Bug fixes

• Prevent passing both query string and parsed document to Schema#execute #957
• Prevent invalid names for types #947

1.6.8 (8 Sept 2017)

Breaking changes

• Validate against EnumType value names to match /^[_a-zA-Z][_a-zA-Z0-9]*$/ #915

New features

• Use stdlib forwardable when it's not Ruby 2.4.0 #926
• Improve UnresolvedTypeError message #928
• Add a default field to the Rails generated mutation type #922

Bug fixes

• Find types via directive arguments when traversing the schema #944
• Assign #connection? when building a schema from IDL #941
• Initialize @edge_class to nil #942
• Disallow invalid enum values #915
• Disallow doubly-nested non-null types #916
• Fix Query#selected_operation_name when no selections are present #899
• Fix needless COUNT query for hasNextPage #906
• Fix negative offset with last argument #907
• Fix line/col for ArgumentsAreDefined validation #890
• Fix Sequel error when limit is 0 #892

1.6.7 (11 Aug 2017)

New features

• Add GraphQL.parse_file and AbstractNode#filename #873
• Support .graphql filepaths with Schema.from_definition #872

Bug fixes

• Fix variable usage inside non-null list #888
• Fix unqualified usage of ActiveRecord::Relation #885
• Fix FieldsWillMerge handling of equivalent input objects
• Fix to call prepare: on nested input types

1.6.6 (14 Jul 2017)

New features

• Validate graphql-pro downloads with rake graphql:pro:validate[$VERSION] #846

Bug fixes

• Remove usage of Rails-only Array.wrap #840
• Fix RelationConnection to count properly when relation contains an alias #838
• Print name of Enum type when a duplicate value is added #843

1.6.5 (13 Jul 2017)

Breaking changes

• Schema#types[](type_name) returns nil when there's no type named type_name (it used to raise RuntimeError). To get an error for missing types, use .fetch instead, for example:

  # Old way:
  MySchema.types[type_name]       # => may raise RuntimeError
  # New way:
  MySchema.types.fetch(type_name) # => may raise KeyError
  

• Schema build steps happen in one pass instead of two passes #819 . This means that instrument(:field) hooks may not access Schema#types, Schema#possible_types or Schema#get_field, since the underlying data hasn't been prepared yet. There's not really a clear upgrade path here. It's a bit of a mess. If you're affected by this, feel free to open an issue and we'll try to find something that works!

Deprecations

• Schema#resolve_type is now called with (abstract_type, obj, ctx) instead of (obj, ctx) #834 . To update, add an unused parameter to the beginning of your resolve_type hook:

  MySchema = GraphQL::Schema.define do
    # Old way:
    resolve_type ->(obj, ctx) { ... }
    # New way:
    resolve_type ->(type, obj, ctx) { ... }
  end
  

New features

• rails g graphql:mutation will add Mutation boilerplate if it wasn't added already #812
• InterfaceType and UnionType both accept resolve_type ->(obj, ctx) { ... } functions for type-specific resolution. This function takes precedence over Schema#resolve_type #829 #834
• Schema#resolve_type is called with three arguments, (abstract_type, obj, ctx), so you can distinguish object type based on interface or union.
• Query#operation_name= may be assigned during query instrumentation #833
• query.context.add_error(err) may be used to add query-level errors #833

Bug fixes

• argument(...) DSL accepts custom keywords #809
• Use single-query max_complexity overrides #812
• Return a client error when InputObjectType receives an array as input #803
• Properly handle raised errors in prepare functions #805
• Fix using as and prepare in argument do ... end blocks #817
• When types are added to the schema with instrument(:field, ...), make sure they're in Schema#types #819
• Raise an error when duplicate EnumValue is created #831
• Properly resolve all query levels breadth-first when using lazy_resolve #835
• Fix tests to run on PostgresQL; Run CI on PostgresQL #814
• When no query string is present, return a client error instead of raising ArgumentError #833
• Properly validate lists containing variables #824

1.6.4 (20 Jun 2017)

New features

• Schema.to_definition sorts fields and arguments alphabetically #775
• validate: false skips static validations in query execution #790

Bug fixes

• graphql:install adds operation_name: params[:operationName] #786
• graphql:install skips graphiql-rails for API-only apps #772
• SerialExecution calls .is_a?(Skip) to avoid user-defined #== methods #794
• prepare: functions which return ExecutionError are properly handled when default values are present #801

1.6.3 (7 Jun 2017)

Bug fixes

• Run multiplex instrumentation when running a single query with a legacy execution strategy #766
• Check each strategy when looking for overridden execution strategy #765
• Correctly wrap Methods with BackwardsCompatibility #763
• Various performance improvements #764
• Don't call #==(other) on user-provided objects (use .is_a? instead) #761
• Support lazy object from custom connection #edge_nodes #762
• If a lazy field returns an invalid null, stop evaluating its siblings #767

1.6.2 (2 Jun 2017)

New features

• Schema.define { default_max_page_size(...) } provides a Connection max_page_size when no other is provided #752
• Schema#get_field(type, field) accepts a string type name #756
• Schema.define { rescue_from(...) } accepts multiple error classes for the handler #758

Bug fixes

• Use *_execution_strategy when executing a single query (doesn't support Schema#multiplex) #755
• Fix NameError when ActiveRecord isn't loaded #747
• Fix Query#mutation? etc to support lazily-loaded AST #754

1.6.1 (28 May 2017)

New Features

• Query#selected_operation_name returns the operation to execute, even if it was inferred (not provided as operation_name:) #746

Bug fixes

• Return nil from Query#operation_name if no operation_name: was provided #746