pbiplint 0.2.2 → 0.2.3

package/README.md

@@ -60,12 +60,18 @@ page.json or visual.json (Power BI Desktop keeps it there too):
 ## What it checks
 
 Every rule from the Microsoft Best Practice Analyzer ruleset, ported so the results match Tabular
-Editor on the same model, with five documented deviations where the source is noisier, or quieter,
+Editor on the same model, with eleven documented deviations where the source is noisier, or quieter,
 than it means to be; and pbiplint's own rules for a year or a date fixed in DAX, such as a measure
-filtered to 2025 or a date table that ends in 2026, and for a DAX user-defined function that nothing
-calls, has a one-word name, or has no description. Five of the Microsoft rules need statistics only
-a live model has; they are listed but not run. Each rule has a page at https://pbiplint.com/rules
-with what it checks, why, how to fix it, and quirks.
+filtered to 2025 or a date table that ends in 2026, for a DAX user-defined function that nothing
+calls, has a one-word name, or has no description, for a visible name that a translated culture
+gives no caption, and for a visible decimal column with no format string. Four of pbiplint's own
+model rules take their test from Tabular Editor's rules, from Tabular Editor 3's built-in set or the
+community's published rule files, and are checked against Tabular Editor on the same model. Five of
+the Microsoft rules need statistics only a live model has; they are listed but not run. A column
+whose TMDL names no type, as Power BI Desktop saves most calculated columns, is left out of the
+thirteen ported rules that test a column's type, where Tabular Editor reads the type from the
+column's DAX. Each rule has a page at https://pbiplint.com/rules with what it checks, why, how to
+fix it, and quirks.
 
 The report layer (PBIR) is read beside the model: a `.Report` folder alone is valid input, and with
 the model beside it the two are paired through `definition.pbir` and checked together. The report