pbiplint 0.1.0 → 0.1.1

package/dist/pbiplint.mjs

@@ -5,7 +5,7 @@ import { mkdirSync, writeFileSync } from "node:fs";
 import { basename as basename2, dirname as dirname4, relative as relative2, resolve as resolve3 } from "node:path";
 
 // ../core/src/version.ts
-var VERSION = "0.1.0";
+var VERSION = "0.1.1";
 
 // ../core/src/engine/config.ts
 var ConfigError = class extends Error {
@@ -2323,20 +2323,21 @@ function parseTmdl(file, text) {
   let pendingDescription = [];
   let descriptionLine = 0;
   let descriptionText = "";
+  const orphanDescription = () => {
+    issues.push({
+      file,
+      line: descriptionLine,
+      text: descriptionText,
+      reason: "description is not followed by a declaration"
+    });
+    pendingDescription = [];
+  };
   let i = 0;
   while (i < lines.length) {
     const raw = lines[i];
     const lineNo = i + 1;
     if (raw.trim() === "") {
-      if (pendingDescription.length) {
-        issues.push({
-          file,
-          line: descriptionLine,
-          text: descriptionText,
-          reason: "description is not followed by a declaration"
-        });
-        pendingDescription = [];
-      }
+      if (pendingDescription.length) orphanDescription();
       i++;
       continue;
     }
@@ -2390,7 +2391,7 @@ function parseTmdl(file, text) {
         j++;
       }
       if (j >= lines.length)
-        issues.push({ file, line: lineNo, text: raw, reason: "unterminated ``` fence" });
+        issues.push({ file, line: lineNo, text: raw, reason: "unterminated code fence" });
       const boundary = j < lines.length ? leadingWs(lines[j]) : 0;
       i = j;
       return out.map((l) => l.slice(Math.min(boundary, leadingWs(l)))).join("\n");
@@ -2445,6 +2446,7 @@ function parseTmdl(file, text) {
     stack[indent] = node;
     i++;
   }
+  if (pendingDescription.length) orphanDescription();
   return { file, roots, issues, lineCount: lines.length };
 }
 
@@ -3132,8 +3134,8 @@ Read more: https://pbiplint.com/rules/large-tables-should-be-partitioned`,
     markdown: "### Why it matters\n\nWith a default summarization, dragging the column onto a visual produces an implicit sum, and it is easy to sum something that should never be summed: a year, a unit price, a percentage, a key. The implicit measure also bypasses the format string and the logic of the real measures, so two visuals of the same thing disagree. With summarization off, the column lands on a visual as a category and the author reaches for a measure.\n\n### How to fix it\n\nIn Power BI Desktop, select the column and set Summarization to Don't summarize under Column tools. In the TMDL file the property is `summarizeBy: none`. Create explicit measures for the aggregations reports need.\n\n### Quirks\n\n- A column with no summarizeBy property is treated as Default, which is not None, so it is flagged.\n\nRead more: https://pbiplint.com/rules/numeric-column-summarize-by"
   },
   OBJECTS_SHOULD_NOT_START_OR_END_WITH_A_SPACE: {
-    text: 'Why it matters\n\nA leading or trailing space is invisible on screen but is part of the name, so "Sales " and "Sales" are two different objects to the engine. That is enough to break a DAX reference, a report visual binding, or a deployment that expects the trimmed name, and the error you get back will name an object that looks perfectly correct. Stray spaces almost always arrive by accident, pasted in or inherited from a source column name, so trimming them is safe and rarely breaks anything downstream. TRIM_OBJECT_NAMES makes the same check across more object types at a lower severity, so every finding here appears there as well.\n\nHow to fix it\n\nRename the object without the space in Power BI Desktop, which updates the visuals and DAX that reference it, or edit the name in the TMDL file.\n\nQuirks\n\n- Narrower scope than TRIM_OBJECT_NAMES: levels, roles, expressions, calculation items, calculated tables, and calculated table columns are not checked here.\n\nRead more: https://pbiplint.com/rules/objects-should-not-start-or-end-with-a-space',
-    markdown: '### Why it matters\n\nA leading or trailing space is invisible on screen but is part of the name, so "Sales " and "Sales" are two different objects to the engine. That is enough to break a DAX reference, a report visual binding, or a deployment that expects the trimmed name, and the error you get back will name an object that looks perfectly correct. Stray spaces almost always arrive by accident, pasted in or inherited from a source column name, so trimming them is safe and rarely breaks anything downstream. `TRIM_OBJECT_NAMES` makes the same check across more object types at a lower severity, so every finding here appears there as well.\n\n### How to fix it\n\nRename the object without the space in Power BI Desktop, which updates the visuals and DAX that reference it, or edit the name in the TMDL file.\n\n### Quirks\n\n- Narrower scope than `TRIM_OBJECT_NAMES`: levels, roles, expressions, calculation items, calculated tables, and calculated table columns are not checked here.\n\nRead more: https://pbiplint.com/rules/objects-should-not-start-or-end-with-a-space'
+    text: 'Why it matters\n\nA leading or trailing space is invisible on screen but is part of the name, so "Sales " and "Sales" are two different objects to the engine. That is enough to break a DAX reference, a report visual binding, or a deployment that expects the trimmed name, and the error you get back will name an object that looks perfectly correct. Stray spaces almost always arrive by accident, pasted in or inherited from a source column name, so trimming them is safe and rarely breaks anything downstream. TRIM_OBJECT_NAMES makes the same check across more object types at a lower severity, so every finding here appears there as well.\n\nHow to fix it\n\nRename the object without the space in Power BI Desktop, which updates the visuals and DAX that reference it, or edit the name in the TMDL file.\n\nQuirks\n\n- Narrower scope than TRIM_OBJECT_NAMES: levels, roles, expressions, calculation items, calculated tables, and calculated table columns are not checked here.\n- In the browser, the "Choose a folder" button in Chrome and Edge does not list a file whose name begins or ends with a space, so a table file named that way is never read on that route and its findings are missing. Drag the folder onto the page, or use the command line, to read it.\n\nRead more: https://pbiplint.com/rules/objects-should-not-start-or-end-with-a-space',
+    markdown: '### Why it matters\n\nA leading or trailing space is invisible on screen but is part of the name, so "Sales " and "Sales" are two different objects to the engine. That is enough to break a DAX reference, a report visual binding, or a deployment that expects the trimmed name, and the error you get back will name an object that looks perfectly correct. Stray spaces almost always arrive by accident, pasted in or inherited from a source column name, so trimming them is safe and rarely breaks anything downstream. `TRIM_OBJECT_NAMES` makes the same check across more object types at a lower severity, so every finding here appears there as well.\n\n### How to fix it\n\nRename the object without the space in Power BI Desktop, which updates the visuals and DAX that reference it, or edit the name in the TMDL file.\n\n### Quirks\n\n- Narrower scope than `TRIM_OBJECT_NAMES`: levels, roles, expressions, calculation items, calculated tables, and calculated table columns are not checked here.\n- In the browser, the "Choose a folder" button in Chrome and Edge does not list a file whose name begins or ends with a space, so a table file named that way is never read on that route and its findings are missing. Drag the folder onto the page, or use the command line, to read it.\n\nRead more: https://pbiplint.com/rules/objects-should-not-start-or-end-with-a-space'
   },
   OBJECTS_WITH_NO_DESCRIPTION: {
     text: "Why it matters\n\nThe description is the tooltip a report author sees when hovering a field in the field list, and it is the only place in the model to say what a measure counts, which currency a column is in, or which of two similar fields to use. Without it, every author works that out from the name, and gets it wrong at about the same rate. Descriptions also feed documentation tools, so the same sentence pays off twice.\n\nHow to fix it\n\nIn Power BI Desktop, open Model view, select the object, and type the Description in the Properties pane. In the TMDL file a description is one or more /// lines directly above the object. With hundreds of objects, Tabular Editor can paste descriptions into many objects at once; the TMDL comment lines need no other tool.\n\nQuirks\n\n- Visibility is the object's own isHidden flag: a visible column inside a hidden table is still reported.\n- A calculation group table is reported once, as a calculation group.\n\nRead more: https://pbiplint.com/rules/objects-with-no-description",
@@ -3288,7 +3290,7 @@ function resolveModel(input) {
 }
 
 // src/main.ts
-var VERSION2 = true ? "0.1.0" : "0.0.0-dev";
+var VERSION2 = true ? "0.1.1" : "0.0.0-dev";
 function listRules() {
   const width = Math.max(...defaultRules.map((r) => r.id.length));
   return defaultRules.map(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pbiplint",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Lint Power BI semantic models (TMDL) for best-practice violations, with text, JSON, SARIF, and Markdown output. Nothing is uploaded.",
   "keywords": [
     "power-bi",
@@ -43,6 +43,6 @@
     "test:bundle": "node dist/pbiplint.mjs --sample --format json > /dev/null; test $? -eq 1"
   },
   "engines": {
-    "node": ">=20"
+    "node": "^20.19.0 || >=22.12.0"
   }
 }