@exhaustive-ui/mcp 22.0.0-alpha.2 → 22.0.0-alpha.4

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.
@@ -2,15 +2,15 @@
2
2
 
3
3
  Theming ExhaustiveUI with alternative styling approaches.
4
4
 
5
- ## Architecture-
5
+ ## Architecture
6
6
 
7
7
  The term unstyled is used to define an alternative styling approach instead of the default theming with design tokens. In unstyled mode the css variables of the design tokens and the css rule sets that utilize them are not included. Here is an example of an Unstyled Select, the core functionality and accessibility is provided whereas styling is not included.
8
8
 
9
- ## Example-
9
+ ## Example
10
10
 
11
11
  Unstyled components require styling using your preferred approach. We recommend using Tailwind CSS with PassThrough attributes, a combination that works seamlessly together. The @exhaustive-ui/tailwindcss even provides special variants such as p-outlined: , p-vertical for the ExhaustiveUI components. The example below demonstrates how to style a button component with Tailwind CSS using PassThrough attributes. Before you begin, refer to the pass through section in the button documentation to familiarize yourself with the component's internal structure and PassThrough attributes. In this example, we'll target the root , label and icon elements to apply custom styles.
12
12
 
13
- ## Global-
13
+ ## Global
14
14
 
15
15
  A global configuration can be created at application level to avoid repetition via the global pt option so that the styles can be shared from a single location. A particular component can still override a global configuration with its own pt property.
16
16
 
@@ -33,7 +33,7 @@ export const appConfig: ApplicationConfig = {
33
33
  };
34
34
  ```
35
35
 
36
- ## Setup-
36
+ ## Setup
37
37
 
38
38
  Unstyled mode is enabled for the whole suite by enabling unstyled option during ExhaustiveUI installation. Alternatively even in the default styled mode, a particular component can still be used as unstyled by adding the unstyled prop of the component.
39
39
 
@@ -0,0 +1,34 @@
1
+ # Update ExhaustiveUI
2
+
3
+ Updating with ng update, Angular version compatibility, and what changes in v22 (Signals API, OnPush, automated migrations).
4
+
5
+ ## Major-versions
6
+
7
+ Each ExhaustiveUI major targets a single Angular major. To move to a new major, update Angular first — the Angular update guide covers that step — then update ExhaustiveUI to the matching major by passing the target version. For example, once Angular v23 and ExhaustiveUI v23 are out, from v22: Review the release notes of the target version for breaking changes before you start.
8
+
9
+ ```bash
10
+ ng update @angular/core@23 @angular/cli@23
11
+ ng update @exhaustive-ui/core@23
12
+ ```
13
+
14
+ ## Ng-update
15
+
16
+ Run ng update without arguments at any time to list the updates available in your workspace, ExhaustiveUI included. To update within the current major, pass the main package. The Angular CLI resolves the rest: @exhaustive-ui/core declares all its companion packages as a group, so every installed @exhaustive-ui/* package — themes, locale, Tailwind CSS plugin and the internal runtime packages — is updated together and the suite cannot end up on mixed versions. Like any ng update run, the command expects a clean git working tree so its changes can be reviewed or reverted in isolation — commit or stash your work first.
17
+
18
+ ## Overview
19
+
20
+ All @exhaustive-ui/core packages — the components, themes, locale definitions, Tailwind CSS plugin and their internal dependencies — are versioned and released together, so an update always moves the whole suite to a single new version. ExhaustiveUI supports ng update , the Angular CLI's own update mechanism, which bumps every installed ExhaustiveUI package in one step and runs any automated code migrations shipped with the new version. Major versions follow Angular's: when a new Angular major ships, a matching ExhaustiveUI major is released for it. Minor and patch releases stay within the same Angular major and are drop-in updates. This page is about updating a project that already uses ExhaustiveUI. To move an existing PrimeNG workspace across, see the migration guide instead.
21
+
22
+ ## Release-notes
23
+
24
+ Every version is published with its notes on the GitHub releases page , covering new features, fixes and any breaking changes or manual steps a release requires. Check the notes for the target version before a major update.
25
+
26
+ ## V22
27
+
28
+ ExhaustiveUI v22 is the first major of the fork. It requires Angular v22 and moves the whole library to the Angular Signals API. Templates keep working as before: inputs are still bound with [name] , two-way bindings with [(name)] , and outputs with (name) . What changes is code that reaches into a component instance. Inputs are signal inputs: read them as component.name() rather than component.name , and set them through a template binding rather than by assignment. Two-way properties such as visible , value or selection are model() signals; call .set() on them from code. Template and child queries are signal queries ( contentChild() , viewChild() , ...), read with a call as well. Components use OnPush change detection, except Table, TreeTable and DynamicDialog. State shared with them should be passed through inputs or signals rather than mutated in place. Templates use the built-in @if / @for control flow, and option lists, menus and paginators track rows by position, so replacing the model no longer recreates every row. Run the update with ng update ; it applies the automated migrations shipped with v22 to your templates and code: styleclass-to-class : styleClass becomes the native class attribute on the components that dropped the input. renamed-inputs : deprecated aliases are renamed to their replacement, e.g. showCloseIcon to closable on Drawer, minLength to minQueryLength on AutoComplete, virtualRowHeight to virtualScrollItemSize on TreeTable. remove-dead-inputs and remove-dead-outputs : bindings of inputs and outputs that already had no effect are removed. config-overlay-options-signal : overlayOptions on the global configuration is a signal; assignments become .set() and reads become calls. Each migration prints the files it changed and the places it left for you to review, with file and line numbers.
29
+
30
+ ```bash
31
+ ng update @angular/core@22 @angular/cli@22
32
+ ng update @exhaustive-ui/core@22
33
+ ```
34
+
@@ -1,9 +1,9 @@
1
1
  {
2
- "generatedAt": "2026-11-20T11:34:28.092Z",
3
- "libraryVersion": "22.0.0-alpha.2",
2
+ "generatedAt": "2026-11-20T14:07:52.655Z",
3
+ "libraryVersion": "22.0.0-alpha.4",
4
4
  "docsGeneratedAt": "2026-11-20",
5
5
  "components": 94,
6
- "guides": 16,
6
+ "guides": 17,
7
7
  "source": "local",
8
8
  "origin": "../../apps/docs/public/llms"
9
9
  }
package/dist/index.d.mts CHANGED
@@ -422,7 +422,7 @@ interface ToolContext {
422
422
  declare const TOOL_NAMES: readonly ["list", "search", "get_component", "get_guide", "get_example", "get_setup", "validate_usage", "version"];
423
423
  declare const STATIC_RESOURCE_URIS: string[];
424
424
  declare const RESOURCE_TEMPLATE_NAMES: string[];
425
- declare const PROMPT_NAMES: readonly ["use_component", "build_form", "theme_component", "migrate_from_primeng", "audit_component_usage"];
425
+ declare const PROMPT_NAMES: readonly ["use_component", "build_form", "theme_component", "migrate_from_primeng", "update_to_v22", "audit_component_usage"];
426
426
  //#endregion
427
427
  //#region src/server.d.ts
428
428
  declare const SERVER_NAME = "@exhaustive-ui/mcp";
package/dist/index.mjs CHANGED
@@ -1064,6 +1064,102 @@ function literalOfBinding(value) {
1064
1064
  return match ? match[1] ?? match[2] : void 0;
1065
1065
  }
1066
1066
 
1067
+ //#endregion
1068
+ //#region src/v22.ts
1069
+ /**
1070
+ * Inputs and outputs removed or renamed in ExhaustiveUI v22, keyed by component tag (`p-` prefix,
1071
+ * case and hyphens ignored). Mirrors the `ng update` migrations of @exhaustive-ui/core
1072
+ * (styleclass-to-class, renamed-inputs, remove-dead-inputs, remove-dead-outputs) so that
1073
+ * validate_usage can name the replacement instead of only reporting an unknown binding.
1074
+ */
1075
+ const STYLE_CLASS_REMOVED = [
1076
+ "toast",
1077
+ "message",
1078
+ "tag",
1079
+ "skeleton",
1080
+ "card",
1081
+ "radiobutton",
1082
+ "progressbar",
1083
+ "divider",
1084
+ "progressspinner",
1085
+ "timeline",
1086
+ "toolbar",
1087
+ "avatar",
1088
+ "chip",
1089
+ "inputgroup",
1090
+ "iconfield",
1091
+ "inputicon",
1092
+ "toggleswitch"
1093
+ ];
1094
+ const RENAMED = {
1095
+ drawer: { showcloseicon: "closable" },
1096
+ paginator: { dropdownappendto: "appendTo" },
1097
+ autocomplete: { minlength: "minQueryLength" },
1098
+ treeselect: {
1099
+ containerstyleclass: "class",
1100
+ containerstyle: "style"
1101
+ },
1102
+ treetable: { virtualrowheight: "virtualScrollItemSize" }
1103
+ };
1104
+ const TRANSITIONS = ["showTransitionOptions", "hideTransitionOptions"];
1105
+ const DEAD_INPUTS = {
1106
+ toast: [
1107
+ "showTransformOptions",
1108
+ "hideTransformOptions",
1109
+ ...TRANSITIONS
1110
+ ],
1111
+ message: TRANSITIONS,
1112
+ overlay: TRANSITIONS,
1113
+ colorpicker: TRANSITIONS,
1114
+ overlaybadge: ["size"],
1115
+ fieldset: ["transitionOptions"],
1116
+ panel: ["transitionOptions"],
1117
+ accordion: ["transitionOptions"],
1118
+ scrolltop: TRANSITIONS,
1119
+ confirmpopup: TRANSITIONS,
1120
+ togglebutton: ["inputId"],
1121
+ popover: [...TRANSITIONS, "ariaCloseLabel"],
1122
+ image: [
1123
+ ...TRANSITIONS,
1124
+ "modalEnterAnimation",
1125
+ "modalLeaveAnimation"
1126
+ ],
1127
+ drawer: ["transitionOptions"],
1128
+ menu: TRANSITIONS,
1129
+ splitbutton: [...TRANSITIONS, "plain"],
1130
+ password: TRANSITIONS,
1131
+ button: ["badgeClass"],
1132
+ tieredmenu: TRANSITIONS,
1133
+ menubar: ["autoZIndex", "baseZIndex"],
1134
+ panelmenu: ["transitionOptions", "tabindex"]
1135
+ };
1136
+ const DEAD_OUTPUTS = { overlay: ["onAnimationStart", "onAnimationDone"] };
1137
+ function tagKey(tag) {
1138
+ return compact(tag.replace(/^p-/i, ""));
1139
+ }
1140
+ function has(list, name) {
1141
+ return !!list?.some((entry) => entry.toLowerCase() === name.toLowerCase());
1142
+ }
1143
+ /** Replacement guidance for an input that no longer exists on `tag`, or undefined when it was not removed in v22. */
1144
+ function removedInputHint(tag, name) {
1145
+ const key = tagKey(tag);
1146
+ const lower = name.toLowerCase();
1147
+ if (lower === "styleclass" && STYLE_CLASS_REMOVED.includes(key)) return {
1148
+ message: "styleClass was removed in v22: use the native class attribute (ng update applies the styleclass-to-class migration).",
1149
+ suggestion: "class"
1150
+ };
1151
+ const renamed = RENAMED[key]?.[lower];
1152
+ if (renamed) return {
1153
+ message: `${name} was renamed to ${renamed} in v22 (ng update applies the renamed-inputs migration).`,
1154
+ suggestion: renamed
1155
+ };
1156
+ if (has(DEAD_INPUTS[key], name)) return { message: `${name} was removed in v22: it had no effect anymore, delete the binding (ng update applies the remove-dead-inputs migration).` };
1157
+ }
1158
+ /** Replacement guidance for an output that no longer exists on `tag`, or undefined when it was not removed in v22. */
1159
+ function removedOutputHint(tag, name) {
1160
+ if (has(DEAD_OUTPUTS[tagKey(tag)], name)) return { message: `${name} was removed in v22: use onOverlayBeforeEnter/onOverlayAfterEnter (show) or onOverlayBeforeLeave/onOverlayAfterLeave (hide) instead (ng update applies the remove-dead-outputs migration).` };
1161
+ }
1162
+
1067
1163
  //#endregion
1068
1164
  //#region src/validate.ts
1069
1165
  /** Attributes any element may carry; never reported as unknown inputs. */
@@ -1297,12 +1393,14 @@ function checkElement(component, element, matches, isOwnElement) {
1297
1393
  const input = inputs.get(lowerName);
1298
1394
  if (!input) {
1299
1395
  if (GLOBAL_ATTRIBUTES.has(lowerName) || lowerName.startsWith("aria-") || lowerName.startsWith("data-") || lowerName.startsWith("ng") || !isOwnElement && NATIVE_ATTRIBUTES.has(lowerName)) break;
1396
+ const removed = isOwnElement ? removedInputHint(element.name, attribute.name) : void 0;
1300
1397
  issues.push({
1301
1398
  kind: "unknown-prop",
1302
1399
  severity: "error",
1303
1400
  name: attribute.name,
1304
- message: `"${attribute.name}" is not an input of ${label}.`,
1305
- allowedProps
1401
+ message: `"${attribute.name}" is not an input of ${label}.${removed ? ` ${removed.message}` : ""}`,
1402
+ allowedProps,
1403
+ ...removed?.suggestion ? { suggestion: removed.suggestion } : {}
1306
1404
  });
1307
1405
  break;
1308
1406
  }
@@ -1325,13 +1423,16 @@ function checkElement(component, element, matches, isOwnElement) {
1325
1423
  case "event":
1326
1424
  if (outputs.has(attribute.name)) break;
1327
1425
  if (inputs.get(lowerName.replace(/change$/, ""))?.twoWay && /change$/i.test(attribute.name)) break;
1328
- if (/^on[A-Z]/.test(attribute.name)) issues.push({
1329
- kind: "unknown-output",
1330
- severity: "error",
1331
- name: attribute.name,
1332
- message: `"${attribute.name}" is not an output of ${label}.`,
1333
- allowedEvents
1334
- });
1426
+ if (/^on[A-Z]/.test(attribute.name)) {
1427
+ const removed = isOwnElement ? removedOutputHint(element.name, attribute.name) : void 0;
1428
+ issues.push({
1429
+ kind: "unknown-output",
1430
+ severity: "error",
1431
+ name: attribute.name,
1432
+ message: `"${attribute.name}" is not an output of ${label}.${removed ? ` ${removed.message}` : ""}`,
1433
+ allowedEvents
1434
+ });
1435
+ }
1335
1436
  break;
1336
1437
  case "twoWay": {
1337
1438
  if (lowerName === "ngmodel") {
@@ -1457,6 +1558,7 @@ const PROMPT_NAMES = [
1457
1558
  "build_form",
1458
1559
  "theme_component",
1459
1560
  "migrate_from_primeng",
1561
+ "update_to_v22",
1460
1562
  "audit_component_usage"
1461
1563
  ];
1462
1564
  const listInput = {
@@ -2212,7 +2314,7 @@ function registerTools(server, ctx) {
2212
2314
  }, (input) => guard(() => getSetupTool(ctx, input)));
2213
2315
  server.registerTool("validate_usage", {
2214
2316
  title: "Validate component usage",
2215
- description: "Check an Angular template or component source against the compiled API of an ExhaustiveUI component: unknown inputs and outputs, invalid literal values, unsupported two-way bindings, deprecated inputs, wrong selectors and PrimeNG imports. Accepts a batch of up to 10 usages.",
2317
+ description: "Check an Angular template or component source against the compiled API of an ExhaustiveUI component: unknown inputs and outputs, invalid literal values, unsupported two-way bindings, deprecated inputs, inputs and outputs removed or renamed in v22 (with their replacement), wrong selectors and PrimeNG imports. Accepts a batch of up to 10 usages.",
2216
2318
  inputSchema: validateUsageInput,
2217
2319
  annotations: readOnly
2218
2320
  }, (input) => guard(() => validateUsageTool(ctx, input)));
@@ -2420,11 +2522,23 @@ const PROMPTS = {
2420
2522
  title: "Migrate from PrimeNG",
2421
2523
  description: "Plan the migration of PrimeNG (or Optimus UI) code to ExhaustiveUI.",
2422
2524
  steps: [
2525
+ "ExhaustiveUI v22 requires Angular v22: the workspace must be on PrimeNG v21, then updated to Angular v22, before running `ng generate @exhaustive-ui/core:migrate-from-primeng`.",
2423
2526
  "Call get_guide for \"faq\" (migration notes) and get_setup for \"angular-cli\".",
2424
2527
  "For each PrimeNG component used, call get_component with the PrimeNG name: renamed components (dropdown, calendar, sidebar, overlaypanel, inputswitch, tabview...) resolve to their ExhaustiveUI equivalent.",
2425
2528
  "Replace `primeng/<name>` imports with `@exhaustive-ui/core/<name>` and call validate_usage on each migrated template."
2426
2529
  ]
2427
2530
  },
2531
+ update_to_v22: {
2532
+ title: "Update to ExhaustiveUI v22",
2533
+ description: "Update an application to ExhaustiveUI v22 (Angular v22, Signals API) and fix what ng update leaves for review.",
2534
+ steps: [
2535
+ "Call get_guide for \"update\" and read its v22 section.",
2536
+ "Update Angular first (`ng update @angular/core@22 @angular/cli@22`), then run `ng update @exhaustive-ui/core@22`; its migrations rewrite styleClass to class, renamed inputs and bindings of removed inputs and outputs, and print what they left for review.",
2537
+ "In TypeScript code that holds a component instance (viewChild, ViewChild, injected component), read inputs as signals (`table.selection()`), write two-way properties with `.set()` (`drawer.visible.set(true)`), and call signal queries.",
2538
+ "Components are OnPush (except Table, TreeTable and DynamicDialog): pass new arrays or objects, or signals, instead of mutating data bound to them in place.",
2539
+ "Call validate_usage on each template that uses a `p-*` element: removed or renamed v22 inputs are reported with their replacement."
2540
+ ]
2541
+ },
2428
2542
  audit_component_usage: {
2429
2543
  title: "Audit ExhaustiveUI usage",
2430
2544
  description: "Review application code for ExhaustiveUI API mismatches.",