@effected/schemastore 0.2.0 → 0.2.1

package/README.md

@@ -240,15 +240,26 @@ const targets = [
   }),
 ];
 
-const program = SchemaPipeline.run(targets).pipe(
-  Effect.provide(Layer.mergeAll(SchemaFile.layer, SchemaValidator.layer)),
-  Effect.provide(NodeServices.layer),
+// One named layer, composed once, provided at the boundary.
+const AppLayer = Layer.mergeAll(SchemaFile.layer, SchemaValidator.layer).pipe(
+  Layer.provide(NodeServices.layer),
 );
 
+const program = SchemaPipeline.run(targets).pipe(Effect.provide(AppLayer));
+
 Effect.runPromise(program).then(console.log);
 // => [{ $id, path, outcome: "written", change: "created", findings: [] }]
 ```
 
+`NodeServices` is composed **into** the layer with `Layer.provide` rather than
+stacked onto the program with a second `Effect.provide`. Both run correctly
+here — `SchemaFile` holds no state, so nothing observes the difference — but
+the composed form is the shape to copy. Stacking `Effect.provide` calls at the
+call site is how a layer ends up built more than once, and the first stateful
+service you add is where that starts to matter. Binding the composition to a
+named `const` also makes it reusable: a drift test and the generator that
+provide the same value cannot disagree about what the layer contains.
+
 A target names its schema, its `$id` and where the file goes. `name` is optional and only catalog naming reads it, so a file-only target like the one above does not repeat its path's basename; supply it when you also pass a `version`, since versioned naming is `<name>-<version>.json`.
 
 Both gates' findings normalize into one `PipelineFinding` shape, so a single predicate judges them. Gating is **policy, not mechanism**: `blocking` defaults to `severity === "warning"`, which is what `UnresolvedRef`, `UnknownKeyword` and `DepthExceeded` are. Replace the predicate rather than the loop when you disagree.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/schemastore",
-	"version": "0.2.0",
+	"version": "0.2.1",
 	"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,7 +38,7 @@
 		"./package.json": "./package.json"
 	},
 	"dependencies": {
-		"@effected/semver": "^0.3.1",
+		"@effected/semver": "^0.3.2",
 		"ajv": "^8.20.0"
 	},
 	"peerDependencies": {