@effected/yaml 0.19.0 → 0.19.2

package/Yaml.js

@@ -151,6 +151,13 @@ var YamlStringifyOptions = class extends Schema.Class("YamlStringifyOptions")({
 * `code` field: read the code from the diagnostics —
 * `error.diagnostics[0].code` is the primary failure.
 *
+* @remarks
+* The `message` renders each diagnostic's position 1-based
+* (`line + 1:character + 1`) for human readers — a CLI printing this string
+* shows the line/column a person counts in their editor. The structured
+* {@link YamlDiagnostic} `line`/`character` fields stay 0-based (LSP
+* convention); the offset applies to the rendered message only.
+*
 * @public
 */
 var YamlParseError = class extends Schema.TaggedError()("YamlParseError", {
@@ -159,7 +166,7 @@ var YamlParseError = class extends Schema.TaggedError()("YamlParseError", {
 }) {
 	get message() {
 		const count = this.diagnostics.length;
-		const summary = this.diagnostics.map((d) => `${d.code} at ${d.line}:${d.character}`).join("; ");
+		const summary = this.diagnostics.map((d) => `${d.code} at ${d.line + 1}:${d.character + 1}`).join("; ");
 		return `YAML parse failed with ${count} error${count === 1 ? "" : "s"}: ${summary}`;
 	}
 };

package/YamlLint.js

@@ -279,11 +279,16 @@ var StyleConflict = class extends Schema.Class("StyleConflict")({
 * rule). Unobserved dimensions never conflict: they fall back to the base
 * config's defaults.
 *
+* @remarks
+* The `message` renders each candidate's first-seen position 1-based
+* (`line + 1:character + 1`) for human readers; the structured
+* {@link StyleVoteTally} `line`/`character` fields stay 0-based.
+*
 * @public
 */
 var YamlStyleConflictError = class extends Schema.TaggedError()("YamlStyleConflictError", { conflicts: Schema.Array(StyleConflict) }) {
 	get message() {
-		return this.conflicts.map((conflict) => `Conflicting style for ${conflict.rule}.${conflict.dimension}: ${conflict.candidates.map((c) => `${JSON.stringify(c.value)} (${c.count}×, first at ${c.line}:${c.character})`).join(" vs ")}`).join("; ");
+		return this.conflicts.map((conflict) => `Conflicting style for ${conflict.rule}.${conflict.dimension}: ${conflict.candidates.map((c) => `${JSON.stringify(c.value)} (${c.count}×, first at ${c.line + 1}:${c.character + 1})`).join(" vs ")}`).join("; ");
 	}
 };
 /** Group canonical vote tallies by rule, then dimension (order-preserving). */

package/index.d.ts

@@ -274,6 +274,13 @@ declare const YamlParseError_base: Schema.Class<YamlParseError, Schema.TaggedStr
  * `code` field: read the code from the diagnostics —
  * `error.diagnostics[0].code` is the primary failure.
  *
+ * @remarks
+ * The `message` renders each diagnostic's position 1-based
+ * (`line + 1:character + 1`) for human readers — a CLI printing this string
+ * shows the line/column a person counts in their editor. The structured
+ * {@link YamlDiagnostic} `line`/`character` fields stay 0-based (LSP
+ * convention); the offset applies to the rendered message only.
+ *
  * @public
  */
 export declare class YamlParseError extends YamlParseError_base {
@@ -1784,6 +1791,11 @@ declare const YamlStyleConflictError_base: Schema.Class<YamlStyleConflictError,
  * rule). Unobserved dimensions never conflict: they fall back to the base
  * config's defaults.
  *
+ * @remarks
+ * The `message` renders each candidate's first-seen position 1-based
+ * (`line + 1:character + 1`) for human readers; the structured
+ * {@link StyleVoteTally} `line`/`character` fields stay 0-based.
+ *
  * @public
  */
 export declare class YamlStyleConflictError extends YamlStyleConflictError_base {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/yaml",
-	"version": "0.19.0",
+	"version": "0.19.2",
 	"private": false,
 	"description": "Zero-dependency YAML parsing, editing, formatting and linting as Effect schemas.",
 	"keywords": [
@@ -41,7 +41,7 @@
 		"./package.json": "./package.json"
 	},
 	"peerDependencies": {
-		"effect": "^4.0.0"
+		"effect": "4.0.2"
 	},
 	"engines": {
 		"node": ">=24.11.0"