graphile-settings 4.20.2 → 4.21.1

package/esm/plugins/enable-all-filter-columns.d.ts

@@ -38,7 +38,7 @@ import type { GraphileConfig } from 'graphile-config';
  * and adds `+attribute:filterBy` and `+attribute:orderBy` back to ALL columns, regardless of index status.
  *
  * This means:
- * - All columns will appear in the connection filter's filter argument
+ * - All columns will appear in the connection filter's `where` argument
  * - All columns will appear in the connection's orderBy enum
  * - Developers can filter and sort by any column
  * - It's the developer's/DBA's responsibility to add indexes for frequently filtered/sorted columns

package/esm/plugins/enable-all-filter-columns.js

@@ -37,7 +37,7 @@
  * and adds `+attribute:filterBy` and `+attribute:orderBy` back to ALL columns, regardless of index status.
  *
  * This means:
- * - All columns will appear in the connection filter's filter argument
+ * - All columns will appear in the connection filter's `where` argument
  * - All columns will appear in the connection's orderBy enum
  * - Developers can filter and sort by any column
  * - It's the developer's/DBA's responsibility to add indexes for frequently filtered/sorted columns

package/esm/presets/constructive-preset.d.ts

@@ -31,8 +31,8 @@ import type { GraphileConfig } from 'graphile-config';
  *
  * RELATION FILTERS:
  * - Enabled via connectionFilterRelations: true
- * - Forward: filter child by parent (e.g. allOrders(filter: { clientByClientId: { name: { startsWith: "Acme" } } }))
- * - Backward: filter parent by children (e.g. allClients(filter: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
+ * - Forward: filter child by parent (e.g. allOrders(where: { clientByClientId: { name: { startsWith: "Acme" } } }))
+ * - Backward: filter parent by children (e.g. allClients(where: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
  *
  * USAGE:
  * ```typescript

package/esm/presets/constructive-preset.js

@@ -41,8 +41,8 @@ import { getBucketProvisionerConnection } from '../bucket-provisioner-resolver';
  *
  * RELATION FILTERS:
  * - Enabled via connectionFilterRelations: true
- * - Forward: filter child by parent (e.g. allOrders(filter: { clientByClientId: { name: { startsWith: "Acme" } } }))
- * - Backward: filter parent by children (e.g. allClients(filter: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
+ * - Forward: filter child by parent (e.g. allOrders(where: { clientByClientId: { name: { startsWith: "Acme" } } }))
+ * - Backward: filter parent by children (e.g. allClients(where: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
  *
  * USAGE:
  * ```typescript
@@ -92,9 +92,11 @@ export const ConstructivePreset = {
     ],
     /**
      * Disable PostGraphile core's condition argument entirely.
-     * All filtering now lives under the `filter` argument via our v5-native
-     * graphile-connection-filter plugin. Search, BM25, pgvector, and PostGIS
-     * filter fields all hook into `isPgConnectionFilter` instead of `isPgCondition`.
+     * All filtering now lives under the `where` argument via our v5-native
+     * graphile-connection-filter plugin (which renames the default `filter`
+     * argument to `where` via `connectionFilterArgumentName: 'where'`).
+     * Search, BM25, pgvector, and PostGIS filter fields all hook into
+     * `isPgConnectionFilter` instead of `isPgCondition`.
      */
     disablePlugins: [
         'PgConditionArgumentPlugin',
@@ -103,7 +105,7 @@ export const ConstructivePreset = {
     /**
      * Connection Filter Plugin Configuration
      *
-     * These options control what fields appear in the `filter` argument on connections.
+     * These options control what fields appear in the `where` argument on connections.
      * Our v5-native graphile-connection-filter plugin controls relation filters via the
      * `connectionFilterRelations` option passed to ConnectionFilterPreset().
      *
@@ -129,13 +131,13 @@ export const ConstructivePreset = {
         /**
          * connectionFilterLogicalOperators: true (default)
          * Keeps `and`, `or`, `not` operators for combining filter conditions.
-         * Example: filter: { or: [{ name: { eq: "foo" } }, { name: { eq: "bar" } }] }
+         * Example: where: { or: [{ name: { eq: "foo" } }, { name: { eq: "bar" } }] }
          */
         connectionFilterLogicalOperators: true,
         /**
          * connectionFilterArrays: true (default)
          * Allows filtering on PostgreSQL array columns.
-         * Example: filter: { tags: { contains: ["important"] } }
+         * Example: where: { tags: { contains: ["important"] } }
          */
         connectionFilterArrays: true,
         /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "graphile-settings",
-  "version": "4.20.2",
+  "version": "4.21.1",
   "author": "Constructive <developers@constructive.io>",
   "description": "graphile settings",
   "main": "index.js",
@@ -30,37 +30,37 @@
   },
   "dependencies": {
     "@aws-sdk/client-s3": "^3.1009.0",
-    "@constructive-io/bucket-provisioner": "^0.2.1",
-    "@constructive-io/graphql-env": "^3.5.4",
-    "@constructive-io/graphql-types": "^3.4.4",
-    "@constructive-io/s3-streamer": "^2.17.4",
-    "@constructive-io/upload-names": "^2.10.2",
+    "@constructive-io/bucket-provisioner": "^0.3.0",
+    "@constructive-io/graphql-env": "^3.6.0",
+    "@constructive-io/graphql-types": "^3.5.0",
+    "@constructive-io/s3-streamer": "^2.18.0",
+    "@constructive-io/upload-names": "^2.11.0",
     "@dataplan/json": "1.0.0",
     "@dataplan/pg": "1.0.0",
     "@graphile-contrib/pg-many-to-many": "2.0.0-rc.2",
-    "@pgpmjs/logger": "^2.5.2",
-    "@pgpmjs/types": "^2.21.0",
+    "@pgpmjs/logger": "^2.6.0",
+    "@pgpmjs/types": "^2.22.0",
     "@pgsql/quotes": "^17.1.0",
     "cors": "^2.8.6",
     "express": "^5.2.1",
     "grafast": "1.0.0",
     "grafserv": "1.0.0",
-    "graphile-bucket-provisioner-plugin": "0.2.1",
+    "graphile-bucket-provisioner-plugin": "0.3.0",
     "graphile-build": "5.0.0",
     "graphile-build-pg": "5.0.0",
     "graphile-config": "1.0.0",
-    "graphile-connection-filter": "^1.4.1",
-    "graphile-postgis": "^2.10.1",
-    "graphile-presigned-url-plugin": "^0.4.1",
-    "graphile-search": "^1.6.1",
-    "graphile-sql-expression-validator": "^2.6.2",
-    "graphile-upload-plugin": "^2.5.2",
+    "graphile-connection-filter": "^1.5.0",
+    "graphile-postgis": "^2.11.1",
+    "graphile-presigned-url-plugin": "^0.5.0",
+    "graphile-search": "^1.7.0",
+    "graphile-sql-expression-validator": "^2.7.0",
+    "graphile-upload-plugin": "^2.6.0",
     "graphile-utils": "5.0.0",
     "graphql": "16.13.0",
     "inflekt": "^0.7.1",
     "lru-cache": "^11.2.7",
     "pg": "^8.20.0",
-    "pg-query-context": "^2.9.2",
+    "pg-query-context": "^2.10.0",
     "pg-sql2": "5.0.0",
     "postgraphile": "5.0.0",
     "request-ip": "^3.3.0",
@@ -71,10 +71,10 @@
     "@types/express": "^5.0.6",
     "@types/pg": "^8.18.0",
     "@types/request-ip": "^0.0.41",
-    "graphile-test": "^4.8.1",
+    "graphile-test": "^4.9.0",
     "makage": "^0.3.0",
     "nodemon": "^3.1.14",
-    "pgsql-test": "^4.8.1",
+    "pgsql-test": "^4.9.0",
     "ts-node": "^10.9.2"
   },
   "keywords": [
@@ -84,5 +84,5 @@
     "constructive",
     "graphql"
   ],
-  "gitHead": "1b2f42363c80172c1305b103d9394c403b3cebea"
+  "gitHead": "da90c33c7bde52c26611509c438fae42cec48b98"
 }

package/plugins/enable-all-filter-columns.d.ts

@@ -38,7 +38,7 @@ import type { GraphileConfig } from 'graphile-config';
  * and adds `+attribute:filterBy` and `+attribute:orderBy` back to ALL columns, regardless of index status.
  *
  * This means:
- * - All columns will appear in the connection filter's filter argument
+ * - All columns will appear in the connection filter's `where` argument
  * - All columns will appear in the connection's orderBy enum
  * - Developers can filter and sort by any column
  * - It's the developer's/DBA's responsibility to add indexes for frequently filtered/sorted columns

package/plugins/enable-all-filter-columns.js

@@ -40,7 +40,7 @@ exports.EnableAllFilterColumnsPreset = exports.EnableAllFilterColumnsPlugin = vo
  * and adds `+attribute:filterBy` and `+attribute:orderBy` back to ALL columns, regardless of index status.
  *
  * This means:
- * - All columns will appear in the connection filter's filter argument
+ * - All columns will appear in the connection filter's `where` argument
  * - All columns will appear in the connection's orderBy enum
  * - Developers can filter and sort by any column
  * - It's the developer's/DBA's responsibility to add indexes for frequently filtered/sorted columns

package/presets/constructive-preset.d.ts

@@ -31,8 +31,8 @@ import type { GraphileConfig } from 'graphile-config';
  *
  * RELATION FILTERS:
  * - Enabled via connectionFilterRelations: true
- * - Forward: filter child by parent (e.g. allOrders(filter: { clientByClientId: { name: { startsWith: "Acme" } } }))
- * - Backward: filter parent by children (e.g. allClients(filter: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
+ * - Forward: filter child by parent (e.g. allOrders(where: { clientByClientId: { name: { startsWith: "Acme" } } }))
+ * - Backward: filter parent by children (e.g. allClients(where: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
  *
  * USAGE:
  * ```typescript

package/presets/constructive-preset.js

@@ -44,8 +44,8 @@ const bucket_provisioner_resolver_1 = require("../bucket-provisioner-resolver");
  *
  * RELATION FILTERS:
  * - Enabled via connectionFilterRelations: true
- * - Forward: filter child by parent (e.g. allOrders(filter: { clientByClientId: { name: { startsWith: "Acme" } } }))
- * - Backward: filter parent by children (e.g. allClients(filter: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
+ * - Forward: filter child by parent (e.g. allOrders(where: { clientByClientId: { name: { startsWith: "Acme" } } }))
+ * - Backward: filter parent by children (e.g. allClients(where: { ordersByClientId: { some: { total: { greaterThan: 1000 } } } }))
  *
  * USAGE:
  * ```typescript
@@ -95,9 +95,11 @@ exports.ConstructivePreset = {
     ],
     /**
      * Disable PostGraphile core's condition argument entirely.
-     * All filtering now lives under the `filter` argument via our v5-native
-     * graphile-connection-filter plugin. Search, BM25, pgvector, and PostGIS
-     * filter fields all hook into `isPgConnectionFilter` instead of `isPgCondition`.
+     * All filtering now lives under the `where` argument via our v5-native
+     * graphile-connection-filter plugin (which renames the default `filter`
+     * argument to `where` via `connectionFilterArgumentName: 'where'`).
+     * Search, BM25, pgvector, and PostGIS filter fields all hook into
+     * `isPgConnectionFilter` instead of `isPgCondition`.
      */
     disablePlugins: [
         'PgConditionArgumentPlugin',
@@ -106,7 +108,7 @@ exports.ConstructivePreset = {
     /**
      * Connection Filter Plugin Configuration
      *
-     * These options control what fields appear in the `filter` argument on connections.
+     * These options control what fields appear in the `where` argument on connections.
      * Our v5-native graphile-connection-filter plugin controls relation filters via the
      * `connectionFilterRelations` option passed to ConnectionFilterPreset().
      *
@@ -132,13 +134,13 @@ exports.ConstructivePreset = {
         /**
          * connectionFilterLogicalOperators: true (default)
          * Keeps `and`, `or`, `not` operators for combining filter conditions.
-         * Example: filter: { or: [{ name: { eq: "foo" } }, { name: { eq: "bar" } }] }
+         * Example: where: { or: [{ name: { eq: "foo" } }, { name: { eq: "bar" } }] }
          */
         connectionFilterLogicalOperators: true,
         /**
          * connectionFilterArrays: true (default)
          * Allows filtering on PostgreSQL array columns.
-         * Example: filter: { tags: { contains: ["important"] } }
+         * Example: where: { tags: { contains: ["important"] } }
          */
         connectionFilterArrays: true,
         /**