@effected/config-file 0.14.0 → 0.14.2

package/ConfigFile.js

@@ -466,6 +466,14 @@ var ConfigFile = class {
 	* and provide that const — do not call `ConfigFile.layer(...)` inline at each
 	* provide site.
 	*
+	* `tag` is a {@link ConfigFile.Service} key — its service type
+	* `ConfigFileShape<A>` for the schema's `A`. A key whose shape adds members
+	* (`ConfigFileShape<A> & { … }`) is a compile error, reported as an argument
+	* "not assignable to parameter of type 'never'", because this layer could not
+	* supply them. The check cannot see through method-syntax parameter
+	* bivariance: a member redeclared as a method with a wider parameter still
+	* compiles.
+	*
 	* @example
 	* ```ts
 	* import { ConfigFile, ConfigResolver, JsonCodec, MergeStrategy } from "@effected/config-file";
@@ -503,6 +511,9 @@ var ConfigFile = class {
 	* so cleanup runs on release without surfacing `Scope` in the layer's
 	* requirements.
 	*
+	* `tag` takes the same `ConfigFileShape<A>` key as {@link ConfigFile.layer},
+	* with the same check: a shape that adds members is a compile error.
+	*
 	* @example
 	* ```ts
 	* const TestConfig = ConfigFile.testLayer(AppConfig, {

package/index.d.ts

@@ -950,6 +950,14 @@ export declare class ConfigFile {
    * and provide that const — do not call `ConfigFile.layer(...)` inline at each
    * provide site.
    *
+   * `tag` is a {@link ConfigFile.Service} key — its service type
+   * `ConfigFileShape<A>` for the schema's `A`. A key whose shape adds members
+   * (`ConfigFileShape<A> & { … }`) is a compile error, reported as an argument
+   * "not assignable to parameter of type 'never'", because this layer could not
+   * supply them. The check cannot see through method-syntax parameter
+   * bivariance: a member redeclared as a method with a wider parameter still
+   * compiles.
+   *
    * @example
    * ```ts
    * import { ConfigFile, ConfigResolver, JsonCodec, MergeStrategy } from "@effected/config-file";
@@ -966,7 +974,7 @@ export declare class ConfigFile {
    * });
    * ```
    */
-  static readonly layer: <Self, A, I, RR = never>(tag: Context.Key<Self, ConfigFileShape<A>>, options: ConfigFileOptions<A, I, RR>) => Layer.Layer<Self, never, FileSystem.FileSystem | Path.Path | RR>;
+  static readonly layer: <Self, A, I, RR = never, S extends ConfigFileShape<A> = ConfigFileShape<A>>(tag: Context.Key<Self, S> & Context.Key<Self, ConfigFileShape<A>> & ([ConfigFileShape<NoInfer<A>>] extends [S] ? unknown : never), options: ConfigFileOptions<A, I, RR>) => Layer.Layer<Self, never, FileSystem.FileSystem | Path.Path | RR>;
   /**
    * A scoped layer that seeds `files` into a temp directory, wires the **real**
    * live implementation over them, and removes the directory when the scope
@@ -987,6 +995,9 @@ export declare class ConfigFile {
    * so cleanup runs on release without surfacing `Scope` in the layer's
    * requirements.
    *
+   * `tag` takes the same `ConfigFileShape<A>` key as {@link ConfigFile.layer},
+   * with the same check: a shape that adds members is a compile error.
+   *
    * @example
    * ```ts
    * const TestConfig = ConfigFile.testLayer(AppConfig, {
@@ -997,7 +1008,7 @@ export declare class ConfigFile {
    * }).pipe(Layer.provide(NodeServices.layer));
    * ```
    */
-  static readonly testLayer: <Self, A, I>(tag: Context.Key<Self, ConfigFileShape<A>>, options: ConfigFileTestOptions<A, I>) => Layer.Layer<Self, never, FileSystem.FileSystem | Path.Path>;
+  static readonly testLayer: <Self, A, I, S extends ConfigFileShape<A> = ConfigFileShape<A>>(tag: Context.Key<Self, S> & Context.Key<Self, ConfigFileShape<A>> & ([ConfigFileShape<NoInfer<A>>] extends [S] ? unknown : never), options: ConfigFileTestOptions<A, I>) => Layer.Layer<Self, never, FileSystem.FileSystem | Path.Path>;
   /**
    * Read, decode and validate one explicit path — no service, no layer, no tag.
    *

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/config-file",
-	"version": "0.14.0",
+	"version": "0.14.2",
 	"private": false,
 	"description": "Composable config file loading for Effect: JSON, JSONC, YAML and TOML codecs, resolution strategies, and merge behaviors.",
 	"keywords": [