@vantreeseba/drizzle-graphql 14.0.0 → 15.0.0

package/dist/index.d.cts

@@ -6,7 +6,7 @@ import "drizzle-orm/pg-core/query-builders/query";
 import { SQLiteAsyncDatabase } from "drizzle-orm/sqlite-core";
 import "drizzle-orm/sqlite-core/query-builders/query";
 import { ASTNode, GraphQLEnumType, GraphQLError, GraphQLFieldResolver, GraphQLInputObjectType, GraphQLInputType, GraphQLList, GraphQLNonNull, GraphQLObjectType, GraphQLOutputType, GraphQLResolveInfo, GraphQLScalarType, GraphQLSchema } from "graphql";
-import { GraphQLDate, GraphQLDateTime, GraphQLJSON, GraphQLUUID } from "graphql-scalars";
+import { GraphQLDateTime, GraphQLJSON, GraphQLUUID } from "graphql-scalars";
 //#region src/util/type-naming.d.ts
 /** A word the rules decline to decide. Widens the keys derived from it rather than guessing. */
 type Unresolved = string;
@@ -2570,6 +2570,18 @@ declare const GraphQLBigIntString: GraphQLScalarType<string, string>;
  * non-numeric strings (including 'NaN' and 'Infinity').
  */
 declare const GraphQLDecimalString: GraphQLScalarType<string, string>;
+/**
+ * A calendar day — `date` columns, whichever `mode` drizzle reads them in. Always transported
+ * as an RFC 3339 `full-date` string (`YYYY-MM-DD`), in both directions: it has no time and no
+ * offset, so there is nothing for a client's timezone to shift. `graphql-scalars`' own
+ * `GraphQLDate` is deliberately not used: its `parseValue` returns a JS `Date`, so the same
+ * scalar would be a string on the way out and an instant on the way in.
+ *
+ * Input accepts only a `YYYY-MM-DD` string naming a real day (`2026-02-30` and datetime
+ * strings are rejected) and hands it on unchanged. Output also accepts a JS `Date`, read as
+ * the UTC day it encodes.
+ */
+declare const GraphQLDate: GraphQLScalarType<string, string>;
 //#endregion
 //#region src/util/selection.d.ts
 /** Options shared by {@link selectionToWith} and {@link resolveSelection}. */

package/dist/index.d.ts

@@ -3,7 +3,7 @@ import { MySqlAsyncDatabase } from "drizzle-orm/mysql-core";
 import { PgAsyncDatabase } from "drizzle-orm/pg-core";
 import { SQLiteAsyncDatabase } from "drizzle-orm/sqlite-core";
 import { ASTNode, GraphQLEnumType, GraphQLError, GraphQLFieldResolver, GraphQLInputObjectType, GraphQLInputType, GraphQLList, GraphQLNonNull, GraphQLObjectType, GraphQLOutputType, GraphQLResolveInfo, GraphQLScalarType, GraphQLSchema } from "graphql";
-import { GraphQLDate, GraphQLDateTime, GraphQLJSON, GraphQLUUID } from "graphql-scalars";
+import { GraphQLDateTime, GraphQLJSON, GraphQLUUID } from "graphql-scalars";
 import "drizzle-orm/mysql-core/query-builders/query";
 import "drizzle-orm/pg-core/query-builders/query";
 import "drizzle-orm/sqlite-core/query-builders/query";
@@ -2570,6 +2570,18 @@ declare const GraphQLBigIntString: GraphQLScalarType<string, string>;
  * non-numeric strings (including 'NaN' and 'Infinity').
  */
 declare const GraphQLDecimalString: GraphQLScalarType<string, string>;
+/**
+ * A calendar day — `date` columns, whichever `mode` drizzle reads them in. Always transported
+ * as an RFC 3339 `full-date` string (`YYYY-MM-DD`), in both directions: it has no time and no
+ * offset, so there is nothing for a client's timezone to shift. `graphql-scalars`' own
+ * `GraphQLDate` is deliberately not used: its `parseValue` returns a JS `Date`, so the same
+ * scalar would be a string on the way out and an instant on the way in.
+ *
+ * Input accepts only a `YYYY-MM-DD` string naming a real day (`2026-02-30` and datetime
+ * strings are rejected) and hands it on unchanged. Output also accepts a JS `Date`, read as
+ * the UTC day it encodes.
+ */
+declare const GraphQLDate: GraphQLScalarType<string, string>;
 //#endregion
 //#region src/util/selection.d.ts
 /** Options shared by {@link selectionToWith} and {@link resolveSelection}. */