v3.2.2

Fixed

• Improves the error message surfaced in cases where FROID generates an empty
  key.

v3.2.1

Fixed

• Fixes a case where sub-entity keys failed to roll up properly to referencing
  entity keys when a value type was in-between.

v3.2.0

Added

• Added a new option for an omittedEntityQualifier to re-evaluate and include
  entities that may have been erroneously omitted by the nodeQualifier. This
  provided the flexibility to fix missing entities while preserving previous
  behavior

v3.1.1

Fix

• The FroidSchema class does not include all enum values found across subgraphs when enum definitions differ.

v3.1.0

• Added a new FroidSchema class to test the next version of FROID schema generation.
• FROID schema is now sorted (both new and old version) and include documentation string.

v3.0.1

Fix

• Applying the @tag directive to an entity's id field could fail if the only @tag directive in the entity was applied to a field argument. This fix now considers field argument @tags as well as field @tags when selecting the id field's @tag(s).

v3.0.0

Breaking

• The federation version is no longer provided as an enum value. It must now be provided as a string of either v1 or a valid v2.x version (examples: v2.1, v2.3, etc.).
• Fixes to complex key schema generation and federation v1 value type schema generation could effect the generated schema. Please carefully compare schema generated with the previous version against schema generated after upgrading.

Added

• Added support for a custom key sorter. This allows for a custom key preference to be applied prior to selecting the first key.
• Added support for explicitly defining the federation version, either v1 or a valid v2.x version (examples: v2.1, v2.3, etc.)

Fix

• In some cases, if a complex key included a nested entity but was not using the entity's key, schema generation would fail to include the nested entity's key field(s).
• In some cases, if a type appeared in multiple subgraphs and was being used in multiple complex keys but with different field selections, not all fields would be included in the generated schema.
• When generating Federation v1 schema, value types would erroneously receive the extend keyword and their fields would erroneously receive the @external directive.

v2.2.0

Added

• Add support for a custom schema node qualifier when generating node-relay schema so users can determine whether or not to include an entity in the generated node-relay schema based on custom criteria

v2.1.0

Added

• support subgraphs using @interfaceObject by omitting @interfaceObjects prior to generation of node relay schema.

v2.0.1

Fix

• Sort the key values encoded in an id to ensure they are deterministically
  generated