Bug fixes for v2.16.0: Fragments, relationship types, and merge mutations

[michaeldgraham]

Query API

• Fragments
  
  
  • Fixes Invalid input in generated query when using inline fragments inside fragments #429 - Invalid input in generated query when using inline fragments inside fragments
    
    When querying an interface type, a fragment can now be used on that same interface type:
    • query only interface type fields using fragments
    • query fields on interface and implementing object type using only fragments
    • query fields on interface and implementing object types using only fragments
      
      
  • Fixes Regression in v2.13.0 #406 - Regression in v2.13.0
    
    When querying an object type, a fragment can now be used on an interface implemented by that object:
    
    • query fields on object type using inline fragment on implemented interface
    • query fields on object type using only fragments on implemented interface

• Relationship Types
  
  

  • Fixes Errors adding _id to @relation types #234 - Errors adding _id to @relation types
    
    When using relationship types, the Neo4j internal ID is now generated and translated appropriately. Corresponding _id_asc and _id_desc values are also generated for the relationship type's ordering enum. Because it is not recommended for unique selection, relationship field arguments are not generated for the _id field.

    • query for relationship internal ID
    • query for interfaced relationship internal ID
    • query relationship properties and order by internal ID
      
      

  • Fixes Error when schema contains array of properties on relationship  #490 - Error when schema contains array of properties on relationship,br>
    
    This issue occurred during augmentation, when generating the orderBy field argument and enum type for a relationship type that does not have at least one non-list scalar field. There is currently no support for for ordering list type scalar fields or relationship fields, so in such a case an ordering enum and its field argument should not be generated. Although the enum type was not being generated, corresponding field arguments on the given relationship field were, resulting in the error noted in the issue. It is also generally prevented by the fix for Errors adding _id to @relation types #234, given that relationship types will now have at least an _id field, and so at least _id_asc and _id_desc ordering fields. Until current behavior changes, the propertyFieldExists function in fields.js has been updated to directly fix this issue.

Mutation API

• Merge
  
  

  • Fixes Not getting Merge Mutations from makeAugmentedSchema  #440 - Not getting Merge Mutations from makeAugmentedSchema
    
    Merge node mutations are now generated even when the type does not have at least 1 field that could be updated. The generation of these mutations was inappropriately prevented, requiring there to be at least 1 field to be used in the case of property updates.

    • Merge node mutation using only primary key
      
      

  • Fixes MergeMyType(MyType: $example) isn´t working #382 - MergeMyType(MyType: $example) isn´t working
    
    This is currently working, so this test has been added to demonstrate the translation:

    • Merge node mutation using argument for field with the same name as merged type