@effected/config-file 0.7.0 → 0.8.0

package/ConfigProvider.js

@@ -3,7 +3,7 @@ import { ConfigProvider, Effect } from "effect";
 //#region src/ConfigProvider.ts
 /**
 * Expose a loaded, merged, schema-validated document as a v4 `ConfigProvider`,
-* so it can be read through `Config.string("port")` and layered beneath other
+* so it can be read through `Config.String("port")` and layered beneath other
 * providers.
 *
 * @remarks
@@ -20,7 +20,7 @@ import { ConfigProvider, Effect } from "effect";
 *    is the exact class of lie this port exists to undo.
 * 2. **Nested keys are structural, not dotted.** `fromUnknown` descends one path
 *    segment at a time, so `{ db: { host } }` is reached with
-*    `Config.nested(Config.string("host"), "db")` — never `Config.string("db.host")`,
+*    `Config.nested(Config.String("host"), "db")` — never `Config.String("db.host")`,
 *    which is looked up as a single literal key and fails. No flattening happens
 *    here, because none is needed.
 * 3. **The decoded value is handed over as-is.** `fromUnknown` descends with
@@ -34,7 +34,7 @@ import { ConfigProvider, Effect } from "effect";
 *    `Expected string, got undefined` — so a `Config` read of a present `Date`
 *    field looks exactly like a typo in the key name. An `Option.some`
 *    descends as a record carrying Effect's internal `value` own-property, so
-*    `Config.nested(Config.string("value"), "field")` happens to read the
+*    `Config.nested(Config.String("value"), "field")` happens to read the
 *    wrapped value straight through — an internal representation, not a
 *    supported spelling. An `Option.none` has no own keys and so reads as
 *    absent, making `Some` and `None` asymmetric. None of this is a supported

package/index.d.ts

@@ -980,7 +980,7 @@ export declare class ConfigMigration {
 //#region src/ConfigProvider.d.ts
 /**
  * Expose a loaded, merged, schema-validated document as a v4 `ConfigProvider`,
- * so it can be read through `Config.string("port")` and layered beneath other
+ * so it can be read through `Config.String("port")` and layered beneath other
  * providers.
  *
  * @remarks
@@ -997,7 +997,7 @@ export declare class ConfigMigration {
  *    is the exact class of lie this port exists to undo.
  * 2. **Nested keys are structural, not dotted.** `fromUnknown` descends one path
  *    segment at a time, so `{ db: { host } }` is reached with
- *    `Config.nested(Config.string("host"), "db")` — never `Config.string("db.host")`,
+ *    `Config.nested(Config.String("host"), "db")` — never `Config.String("db.host")`,
  *    which is looked up as a single literal key and fails. No flattening happens
  *    here, because none is needed.
  * 3. **The decoded value is handed over as-is.** `fromUnknown` descends with
@@ -1011,7 +1011,7 @@ export declare class ConfigMigration {
  *    `Expected string, got undefined` — so a `Config` read of a present `Date`
  *    field looks exactly like a typo in the key name. An `Option.some`
  *    descends as a record carrying Effect's internal `value` own-property, so
- *    `Config.nested(Config.string("value"), "field")` happens to read the
+ *    `Config.nested(Config.String("value"), "field")` happens to read the
  *    wrapped value straight through — an internal representation, not a
  *    supported spelling. An `Option.none` has no own keys and so reads as
  *    absent, making `Some` and `None` asymmetric. None of this is a supported

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/config-file",
-	"version": "0.7.0",
+	"version": "0.8.0",
 	"private": false,
 	"description": "Composable config file loading for Effect: JSON, JSONC, YAML and TOML codecs, resolution strategies, and merge behaviors.",
 	"keywords": [
@@ -43,11 +43,11 @@
 		"./package.json": "./package.json"
 	},
 	"peerDependencies": {
-		"@effected/jsonc": "^0.9.0",
-		"@effected/toml": "^0.6.0",
-		"@effected/walker": "^0.7.0",
-		"@effected/yaml": "^0.14.0",
-		"effect": "4.0.0-rc.112"
+		"@effected/jsonc": "^0.11.0",
+		"@effected/toml": "^0.7.0",
+		"@effected/walker": "^0.8.0",
+		"@effected/yaml": "^0.15.0",
+		"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"
     }
   ]
 }