Skip to content

CHANGELOG.md

Latest commit

 

History

History
89 lines (59 loc) · 4.2 KB

CHANGELOG.md

File metadata and controls

89 lines (59 loc) · 4.2 KB

0.8.4

  • Fixed casing of AgreementResponse.agreement to remove uppercase A
  • GraphQL peer dependency minimum compatible version downgraded to 14.5.8. (Incompatibilities were between GraphQL & GraphiQL, not this lib.)

0.8.3

  • Added classifiedAs to Organization
  • Added onHandEffect to Action
  • Added defaultUnitOfResource to ResourceSpecification
  • Added RecipeExchange to the recipe module
  • Further modularised schemas to allow economic modules to be used without Agent functionality
  • Updated GraphQL modules to most recent version (15.x series) and configured graphql as a peerDependency to allow broader compatibility

0.8.2

  • Allow overriding options for both buildASTSchema and mergeTypeDefs

0.8.1

  • Allow overriding options to mergeTypeDefs in order to deal with looser validation in extension schemas

0.8.0

  • Added an additional argument to buildSchema to allow passing extension schemas as SDL strings in order to extend core VF with custom domain-specific additions easily
  • Breaking: removed loose AnyType custom scalar and restricted inScopeOf fields to only allow Person | Organization as valid values. Note that implementations may extend the AccountingScope union type if they wish to allow other types of record scoping (eg. groups without collective agency, geographical locations).
  • Breaking: removed all prefixes from toplevel record listing endpoints for sensible autocomplete, and made search endpoint query prefixes into suffixes
  • Breaking: fixed deletion methods taking String when they should receive ID

0.7.1

  • Fix generated TypeScript / Flow types missing "bridging" fields due to misconfiguration of graphql-codegen
  • Fix EconomicEvent appreciation edges linking directly to other events instead of via Appreciation

0.7.0

  • Added descriptions to all input fields, to make interacting with the API more self-documenting
  • Added pagination parameters to all list queries
  • Removed many accounting fields from EconomicEventUpdateParams that should not have been present
  • Added various fields missed in the original conversion:
    • Agent.primaryLocation
    • Scenario.definedAs
  • Fixed missing input fields:
    • basedOn & classifiedAs in ProcessUpdateParams
    • refinementOf in Plan create / update
    • resourceConformsTo in RecipeResource create / update
    • processClassifiedAs in RecipeProcess create / update
    • refinementOf in Scenario create / update
    • ScenarioDefinitionUpdateParams.name
  • Add missing mutations & queries for Claim, Scenario, ScenarioDefinition & SpatialThing
  • Removed pass & fail actions from the set of core verbs (see ValueFlows/#610)

0.6.1

  • Finished some rough edges on modularisation such that you no longer need to explicitly include query and mutation in the list of schemas to buildSchema().

0.6.0

  • Breaking: significant changes to the internal structure of the module to facilitate modular composition of schemas. Now exports a buildSchema function rather than pre-initialised schema object. Use printSchema on the output of buildSchema() for tools which require the input as an SDL schema string, rather than a GraphQLSchema object.

0.5.0

  • Breaking: renames the transfer-complete action to transfer, as the former was confusing for some users
  • Adds missed mutations for Proposal and related records

0.4.3

  • Adds defaultUnitOfEffort to ResourceSpecification as a stop-gap for unit inference in VF0.4 release (see #64)

0.4.2

  • Finalise fields for EconmicResource & EconomicEvent creation & update logic

0.4.1

  • Adds missed mutations for Unit & ProcessSpecification

0.4.0

Updated for ValueFlows 0.4 release.

  • Changed from QUDT to OM ontology for measurements
  • New action metadata
  • Add EconomicResource stage & state attributes
  • Remove before & after time fields on EconomicEvent & Process

0.3.0

Initial release. Rough around the edges, missing many mutations & queries, but the core schema is stable.