@valueflows/vf-graphql - npm Package Compare versions

Comparing version 0.9.0-alpha.6 to 0.9.0-alpha.7

build/observation.js

@@ -268,11 +268,8 @@
   updateEconomicEvent(event: EconomicEventUpdateParams!): EconomicEventResponse!
-  deleteEconomicEvent(revisionId: ID!): Boolean!
 
-  # :TODO: should this be allowed without an originating event? Or should the event be recorded transparently?
   updateEconomicResource(
     resource: EconomicResourceUpdateParams!
   ): EconomicResourceResponse!
-  deleteEconomicResource(revisionId: ID!): Boolean!
 }
 
 `

CHANGELOG.md

@@ -0,1 +1,6 @@
+## 0.9.0-alpha.7
+
+- **Breaking:** removed `deleteEconomicEvent` and `deleteEconomicResource` as there are bookkeeping repercussions for deleting them, even in simple cases.
+- Fixed schema files for `ResourceSpecification` & `ProcessSpecification` history queries being incorrectly named, leading to missing query edges.
+
 ## 0.9.0-alpha.6
@@ -2,0 +7,0 @@

package.json

 {
   "name": "@valueflows/vf-graphql",
-  "version": "0.9.0-alpha.6",
+  "version": "0.9.0-alpha.7",
   "description": "Reference GraphQL implementation of the ValueFlows spec",
@@ -5,0 +5,0 @@ "main": "index.js",

schema-manifest.js

@@ -65,3 +65,2 @@
     'history.geolocation': require('./build/history.geolocation'),
-    'history.knowledge': require('./build/history.knowledge'),
     'history.measurement': require('./build/history.measurement'),
@@ -71,5 +70,7 @@ 'history.observation': require('./build/history.observation'),
     'history.planning': require('./build/history.planning'),
+    'history.process_specification': require('./build/history.process_specification'),
     'history.proposal.agent': require('./build/history.proposal.agent'),
     'history.proposal': require('./build/history.proposal'),
     'history.recipe': require('./build/history.recipe'),
+    'history.resource_specification': require('./build/history.resource_specification'),
     'history.scenario': require('./build/history.scenario'),
@@ -76,0 +77,0 @@ 'intent.filtering': require('./build/intent.filtering'),

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Number of package files

213

increased by0.95%

Worsened metrics

Total package byte prevSize

1374905

decreased by-0.12%

Lines of code

35296

decreased by-0.16%

No dependency changes