@effected/schemastore 0.6.0 → 0.7.0

package/SchemaValidator.js

@@ -1,8 +1,10 @@
 import { KeywordFamilies } from "./KeywordFamilies.js";
 import { Context, Effect, Layer, Schema } from "effect";
 import { Ajv } from "ajv";
+import ajvFormats from "ajv-formats";
 
 //#region src/SchemaValidator.ts
+const addFormats = ajvFormats.default;
 /**
 * Indicates that the validation engine behind the {@link SchemaValidator}
 * contract failed as a *mechanism* — it could not run at all.
@@ -70,7 +72,16 @@ const notStubbed = (method) => () => Effect.die(/* @__PURE__ */ new Error(`Schem
 * The shipped layer registers every declared {@link KeywordFamilies} keyword
 * present in the document before compiling, so ajv strict mode does not
 * reject the language-server families `DocumentLint` deliberately allows —
-* one predicate governs both verdicts.
+* one predicate governs both verdicts. It also registers the standard
+* ajv-formats vocabulary (`date-time`, `date`, `time`, `duration`, `uri`,
+* `uri-reference`, `uri-template`, `url`, `email`, `hostname`, `ipv4`,
+* `ipv6`, `regex`, `uuid`, `json-pointer`, `relative-json-pointer`, …), so a
+* published document can say "this string is an ISO-8601 instant" with a
+* `format` instead of falling back to a `pattern` plus a runtime filter;
+* an UNKNOWN format string remains a strict-mode rejection. The plugin's
+* `formatMaximum` / `formatMinimum` limit keywords are deliberately NOT
+* registered — `DocumentLint` answers those as unknown keywords, and the
+* two verdicts must not drift.
 *
 * @example
 * ```ts
@@ -103,7 +114,10 @@ var SchemaValidator = class SchemaValidator extends Context.Service()("@effected
 	* engine failing as a mechanism.
 	*
 	* `strict` defaults to `true` — SchemaStore's gate. Each call builds its
-	* own ajv instance, so documents sharing an `$id` never collide.
+	* own ajv instance, so documents sharing an `$id` never collide. The
+	* standard ajv-formats vocabulary is registered on every instance, so
+	* `format: "date-time"` (and the rest of the standard set) compiles under
+	* strict mode instead of being rejected as an unknown format.
 	*/
 	static layer = Layer.succeed(SchemaValidator, { validate: (document, options) => Effect.try({
 		try: () => {
@@ -111,6 +125,7 @@ var SchemaValidator = class SchemaValidator extends Context.Service()("@effected
 				strict: options?.strict ?? true,
 				allErrors: true
 			});
+			addFormats(ajv, { keywords: false });
 			const declared = /* @__PURE__ */ new Set();
 			collectDeclaredKeywords(document, declared, 0);
 			try {

package/index.d.ts

@@ -241,7 +241,7 @@ interface StoreDocumentOptions {
   readonly $id: string;
   /**
    * Passed through to core's `Schema.toJsonSchemaDocument`
-   * (`additionalProperties`, `generateDescriptions`,
+   * (`onExcessProperty`, `generateDescriptions`,
    * `includeAnnotationKey`).
    *
    * The declared non-standard keyword families ({@link KeywordFamilies})
@@ -1084,7 +1084,16 @@ declare const SchemaValidator_base: Context.ServiceClass<SchemaValidator, "@effe
  * The shipped layer registers every declared {@link KeywordFamilies} keyword
  * present in the document before compiling, so ajv strict mode does not
  * reject the language-server families `DocumentLint` deliberately allows —
- * one predicate governs both verdicts.
+ * one predicate governs both verdicts. It also registers the standard
+ * ajv-formats vocabulary (`date-time`, `date`, `time`, `duration`, `uri`,
+ * `uri-reference`, `uri-template`, `url`, `email`, `hostname`, `ipv4`,
+ * `ipv6`, `regex`, `uuid`, `json-pointer`, `relative-json-pointer`, …), so a
+ * published document can say "this string is an ISO-8601 instant" with a
+ * `format` instead of falling back to a `pattern` plus a runtime filter;
+ * an UNKNOWN format string remains a strict-mode rejection. The plugin's
+ * `formatMaximum` / `formatMinimum` limit keywords are deliberately NOT
+ * registered — `DocumentLint` answers those as unknown keywords, and the
+ * two verdicts must not drift.
  *
  * @example
  * ```ts
@@ -1117,7 +1126,10 @@ export declare class SchemaValidator extends SchemaValidator_base {
    * engine failing as a mechanism.
    *
    * `strict` defaults to `true` — SchemaStore's gate. Each call builds its
-   * own ajv instance, so documents sharing an `$id` never collide.
+   * own ajv instance, so documents sharing an `$id` never collide. The
+   * standard ajv-formats vocabulary is registered on every instance, so
+   * `format: "date-time"` (and the rest of the standard set) compiles under
+   * strict mode instead of being rejected as an unknown format.
    */
   static readonly layer: Layer.Layer<SchemaValidator>;
   /**

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/schemastore",
-	"version": "0.6.0",
+	"version": "0.7.0",
 	"private": false,
 	"description": "Build, validate, version and publish SchemaStore-shaped Draft-07 JSON Schema documents from Effect Schema sources: document assembly, ajv strict-mode validation, structural lints, catalog entries, canonical JSON and a content-comparing emit pipeline.",
 	"keywords": [
@@ -38,11 +38,12 @@
 		"./package.json": "./package.json"
 	},
 	"dependencies": {
-		"@effected/semver": "^0.6.0",
-		"ajv": "^8.20.0"
+		"@effected/semver": "^0.7.0",
+		"ajv": "^8.20.0",
+		"ajv-formats": "^3.0.1"
 	},
 	"peerDependencies": {
-		"effect": "4.0.0-rc.112"
+		"effect": "4.0.0-rc.115"
 	},
 	"engines": {
 		"node": ">=24.11.0"

package/tsdoc-metadata.json

@@ -5,7 +5,7 @@
   "toolPackages": [
     {
       "packageName": "@microsoft/api-extractor",
-      "packageVersion": "7.59.0"
+      "packageVersion": "7.59.1"
     }
   ]
 }