@webority/repo-checks 0.110.3 → 0.112.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -36,6 +36,7 @@ The `missing-export:<file>` check runs the Biome installed beside the app or in
36
36
  | `android-release-signing` | `android/app/build.gradle` has no guard that throws a `GradleException` when a requested task name contains `release` and a signing setting or the upload key is missing |
37
37
  | `android-edge-to-edge` | `android/gradle.properties` sets `edgeToEdgeEnabled=false` |
38
38
  | `rn-mainactivity-oncreate-bundle:<file>` | A `MainActivity.kt` or `.java` passes a bundle to `super.onCreate`; pass `null` |
39
+ | `metro-bridge:<file>` | A React Native app's entry file (`package.json` `main`, default `index.js`), root `App.js` or `src/App.js` nor any other source file of the app (outside `node_modules`, `ios`, `android` and build output) imports `createMetroBridge` from `@webority/mobile-core/metro` and assigns `globalThis.__METRO_BRIDGE__` from a `createMetroBridge(...)` call inside `if (__DEV__)` in the same file; react-native-procedures.md → Debugging: the development bridge |
39
40
  | `mobile-production-stamps:<file>` | A mobile app's Android manifest or iOS `Expo.plist` points over-the-air updates at the Staging or Development feed, or `android/gradle.properties` carries a `.staging` or `.development` app id, left by `mobile-tools prebuild`. Run `mobile-tools prebuild --env Production` before committing |
40
41
  | `spa-host-immutable-assets:<file>` | A web app's `web.config`, `staticwebapp.config.json`, `_headers` or `spa-host*.json` sets Cache-Control with `immutable` |
41
42
  | `stale-theme-name:<file>` | A web style or source file reads a pre-0.89.0 theme name as a whole token (`var(--radius)`, `--color-primary-ink`). No alias ships for these. Run `webority upgrade 0.89.0 --path <folder>` once, then `webority brand`. `--color-primary-text` is not flagged. Never recorded in the baseline |
@@ -55,8 +56,10 @@ The `missing-export:<file>` check runs the Biome installed beside the app or in
55
56
  | `rename-wrapper:<file>` | A re-export of `@webority/ui-react`, a component whose body only returns one catalogue component, or a `_Name.cshtml` partial that is one `<app-*>` element: import the library name. Counted per file. |
56
57
  | `single-use-component:<file>` | A file under `src/components/<feature>/` (not `layout/`), or a shared partial under `Pages/Shared/` or a `*.Web.Common` project, that fewer than two files use; move it next to the page that uses it. A layout is skipped: a `_…Layout.cshtml` file, or one that a `_ViewStart.cshtml` of the same project names with `Layout = "<name>"`, because areas find it by that name. A Razor file whose first line is `@* layering-allow single-use-component: <reason> *@` is skipped too; a mark with no reason is a finding. Counted per file. |
57
58
  | `error-summary-title:<file>` | A `.cshtml` `<app-error-summary>` sets a `title` with the old generic wording ("Please fix the following", "There were errors"); drop it, the library writes the standard heading. A computed title or one naming the failed action is not counted. Counted per file. |
59
+ | `route-internal-id:<file>` | A route binds a record's internal number: a `.cshtml` `@page` or a C# `[Route]`, `[Http*]` or `Map*` template whose `id` or `...Id` parameter is constrained `int` or `long`, or an `asp-route-*` link that passes a record's `.Id`. Route by the public id (`{publicId:guid}`) instead. An untyped `{id}` is not counted. Counted per file. |
58
60
  | `oversize:<file>` | A `.jsx`, `.tsx` or `.cshtml` file over 600 lines (over 800 says to split it along its concerns). A warning only: it never fails, even outside the baseline. Counted per file. |
59
61
  | `hook:drift` | The root `.husky/pre-commit` is missing or differs from the shared hook this package ships (CRLF is ignored) |
62
+ | `tracked-case:<path>` | A tracked file or folder whose name on disk differs only by letter case, a rename done by hand on a Mac that git never saw; a Linux checkout cannot find the import. Run the `git mv` the message gives. A folder is reported once. Always fails. |
60
63
 
61
64
  Comment lines (`//`, `/*`, `*`) and `.test.` or `.spec.` files are not read by the import checks.
62
65
 
@@ -64,7 +67,9 @@ Comment lines (`//`, `/*`, `*`) and `.test.` or `.spec.` files are not read by t
64
67
 
65
68
  The four rules read every tracked `.scss`, `.css`, `.cshtml`, `.jsx` and `.tsx` file, and each `.js` or
66
69
  `.ts` file that imports `react-native`. They skip a path with a `node_modules`, `dist`, `generated`,
67
- `vendor`, `__tests__` or `__mocks__` segment, a path containing `wwwroot/lib/`, a `.generated.` name,
70
+ `vendor`, `__tests__` or `__mocks__` segment, an email template project folder (`<Product>.Email` or
71
+ `<Product>.Emails`: email clients read no CSS variables, so inline pixels and colours are required there;
72
+ a plain `Email` folder of admin screens stays checked), a path containing `wwwroot/lib/`, a `.generated.` name,
68
73
  a `.min.css` name, a `.test.` or `.spec.` script, and any path the repo lists under `generated[].paths` in
69
74
  `.webority/map.json` (a trailing `/` names a folder; `*` matches within one segment). List a compiled
70
75
  stylesheet there: it bundles the shared theme, so its library rules are not the product's code, and the
@@ -131,6 +136,8 @@ its current value, deleting one that reaches 0; it never adds or raises one.
131
136
 
132
137
  `--baseline-accept <folder> --reason <text>` records debt the owner has accepted: every current finding and count under that folder is added, and a count is raised to its current value, never lowered. Use it only for debt the owner has accepted, and give a reason that names the decision; the reason is kept in `accepted` in the baseline file, and `--baseline-shrink` keeps that entry.
133
138
 
139
+ `--baseline-adopt <rule,...>` records today's findings and counts for rules the baseline has never recorded, such as a rule a new release adds. It refuses a rule the baseline already records, so it never raises an existing entry, and names how many findings and counts it adopted per rule.
140
+
134
141
  `--baseline-init` runs once: it refuses an existing file and folder arguments. When the file is the
135
142
  earlier shape (no `version`), delete it and run `--baseline-init` once from the git root, then review
136
143
  the diff before committing.
@@ -4,6 +4,7 @@
4
4
  "@webority/canvas-kit",
5
5
  "@webority/chat-react",
6
6
  "@webority/insights-react",
7
+ "@webority/markdown-core",
7
8
  "@webority/mobile-chat",
8
9
  "@webority/mobile-core",
9
10
  "@webority/mobile-support",