@exhaustive-ui/mcp 22.0.0-rc.3 → 22.0.1

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.
@@ -1,34 +1,63 @@
1
1
  # Update ExhaustiveUI
2
2
 
3
- Updating with ng update, Angular version compatibility, and what changes in v22 (Signals API, OnPush, automated migrations).
3
+ Updating with ng update, Angular version compatibility, and a summary of what changes in v22.
4
4
 
5
- ## Major-versions
5
+ ## Overview
6
+
7
+ 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
8
+ 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.
9
+
10
+ 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.
11
+
12
+ This page is about updating a project that already uses ExhaustiveUI. To move an existing workspace across, see the guides for
13
+ [PrimeNG](https://exhaustive-ui.com/migration/primeng) and [Optimus UI](https://exhaustive-ui.com/migration/optimus) instead.
14
+
15
+ ## Updating
6
16
 
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.
17
+ Run `ng update` without arguments at any time to list the updates available in your workspace, ExhaustiveUI included.
8
18
 
9
19
  ```bash
10
- ng update @angular/core@23 @angular/cli@23
11
- ng update @exhaustive-ui/core@23
20
+ ng update
12
21
  ```
13
22
 
14
- ## Ng-update
23
+ 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 —
24
+ themes, locale, Tailwind CSS plugin and the internal runtime packages — is updated together and the suite cannot end up on mixed versions.
15
25
 
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.
26
+ ```bash
27
+ ng update @exhaustive-ui/core
28
+ ```
17
29
 
18
- ## Overview
30
+ 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.
19
31
 
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.
32
+ ## Angular Version Compatibility
21
33
 
22
- ## Release-notes
34
+ Each ExhaustiveUI major targets a single Angular major.
23
35
 
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.
36
+ To move to a new major, update Angular first — the [Angular update guide](https://angular.dev/update-guide) covers that step — then update ExhaustiveUI to the matching major by
37
+ passing the target version. For example, once Angular v23 and ExhaustiveUI v23 are out, from v22:
25
38
 
26
- ## V22
39
+ ```bash
40
+ ng update @angular/core@23 @angular/cli@23
41
+ ng update @exhaustive-ui/core@23
42
+ ```
43
+
44
+ Review the release notes of the target version for breaking changes before you start.
27
45
 
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, filterPlaceHolder to filterPlaceholder on Listbox and MultiSelect. renamed-outputs : outputs are renamed to the name the other components use, with the same event payload: onFilterEvent to onFilter on OrderList, selectAllChange to onSelectAllChange on Table, onPanelShow / onPanelHide to onShow / onHide on MultiSelect. renamed-templates : the removetokenicon template of MultiSelect becomes chipicon . 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. removed-exports : Password_VALUE_ACCESSOR becomes PASSWORD_VALUE_ACCESSOR , and the removed p-inplacedisplay / p-inplacecontent wrappers become a span . config-input-style-to-variant : the global inputStyle option, deprecated since v20, becomes inputVariant in provideExhaustive() and on the configuration service. Each migration prints the files it changed and the places it left for you to review, with file and line numbers. A workspace that has just switched to ExhaustiveUI, from PrimeNG with the migrate-from-primeng schematic or from Optimus UI, did not go through ng update . Run the migrations explicitly:
46
+ ## Updating to v22
47
+
48
+ ExhaustiveUI v22 is the first major of the fork. It requires Angular 22 and moves the whole library to the Angular Signals API. Templates keep working as before; code that reaches into a component instance reads inputs with a call and
49
+ writes two-way properties with `.set()`, and components use OnPush change detection. `ng update` applies nine migrations to templates and code and reports what it left for review.
29
50
 
30
51
  ```bash
31
52
  ng update @angular/core@22 @angular/cli@22
32
53
  ng update @exhaustive-ui/core@22
33
54
  ```
34
55
 
56
+ The [migration guide to v22](https://exhaustive-ui.com/migration/v22) covers the update steps from an ExhaustiveUI prerelease, PrimeNG v21 or Optimus UI, each migration and its report, the code changes, and the behavior
57
+ and type changes.
58
+
59
+ ## Release Notes
60
+
61
+ Every version is published with its notes on the [GitHub releases page](https://github.com/e-xiste/exhaustive-ui/releases), covering new features, fixes and any breaking changes or
62
+ manual steps a release requires. Check the notes for the target version before a major update.
63
+
@@ -0,0 +1,221 @@
1
+ # Migrating to v22
2
+
3
+ Moving an application to ExhaustiveUI v22: update steps from an ExhaustiveUI prerelease, PrimeNG v21 or Optimus UI, the automated migrations and their report, the Signals API, OnPush, removed API, behavior and type changes.
4
+
5
+ ## Overview
6
+
7
+ ExhaustiveUI v22 requires Angular 22 and moves every component and directive to the Angular Signals API. Templates bind as before: `[name]`, `[(name)]` and `(name)` keep working. Most of the work is done by
8
+ `ng update`. What is left is code that reaches into a component instance, data mutated in place under OnPush components, and the few places the migrations report.
9
+
10
+ This guide covers three starting points:
11
+
12
+ - **A v22 alpha or release candidate** of ExhaustiveUI: update to 22.0.0 with `ng update`, which runs the migrations. They leave code that is already migrated as it is, so running them again is safe.
13
+ - **PrimeNG v21**: switch to ExhaustiveUI with the `migrate-from-primeng` schematic, then run the v22 migrations explicitly.
14
+ - **Optimus UI v2**, which shares the PrimeNG v21 API: swap the packages and imports, then run the v22 migrations explicitly.
15
+
16
+ Updating later within v22, or to a future major, is covered by the [update guide](https://exhaustive-ui.com/migration/update). Every breaking change below is also listed in the
17
+ [changelog](https://github.com/e-xiste/exhaustive-ui/blob/main/CHANGELOG.md).
18
+
19
+ ## Before you start
20
+
21
+ - **Angular 22.** The peer dependencies are `^22.0.0`. Update Angular first with the [Angular update guide](https://angular.dev/update-guide), and use the Node.js and TypeScript versions it requires.
22
+ - **A clean git working tree.** Commit or stash your work, so the changes made by the migrations can be reviewed, and reverted, on their own.
23
+ - **A build and test run that passes** before you start, so anything that breaks afterwards comes from the update.
24
+ - **PrimeFlex**, if the project uses it: it is not part of the update. The `migrate-from-primeflex` schematic translates its classes to Tailwind CSS, as a separate step.
25
+
26
+ ## Update steps
27
+
28
+ ### From an ExhaustiveUI alpha or release candidate
29
+
30
+ Update Angular, then ExhaustiveUI. Every installed `@exhaustive-ui/*` package moves to 22.0.0 together, and the migrations run.
31
+
32
+ ```bash
33
+ ng update @angular/core@22 @angular/cli@22
34
+ ng update @exhaustive-ui/core@22
35
+ ```
36
+
37
+ ### From PrimeNG v21
38
+
39
+ Update Angular to 22, install ExhaustiveUI and run the `migrate-from-primeng` schematic. It swaps the `primeng`, `@primeuix/*` and PrimeIcons dependencies, rewrites the imports (`primeng/button` becomes
40
+ `@exhaustive-ui/core/button`) and renames the configuration API (`providePrimeNG` becomes `provideExhaustive`). The workspace did not go through `ng update`, so run the v22 migrations explicitly afterwards.
41
+
42
+ ```bash
43
+ ng update @angular/core@22 @angular/cli@22 --force
44
+ npm install @exhaustive-ui/core@22
45
+ ng generate @exhaustive-ui/core:migrate-from-primeng
46
+ ng update @exhaustive-ui/core --migrate-only --from=3.0.0
47
+ ```
48
+
49
+ Projects on PrimeNG v20 or older upgrade to PrimeNG v21 first; the schematic checks the version and refuses otherwise. The [PrimeNG migration guide](https://exhaustive-ui.com/migration/primeng) details each step,
50
+ including the `--force` the Angular update needs while `primeng` is installed.
51
+
52
+ ### From Optimus UI v2
53
+
54
+ Optimus UI v2 has the PrimeNG v21 API under other package names. The `migrate-from-optimus` schematic swaps its packages for their `@exhaustive-ui/*` counterparts and renames the imports, the configuration API and the
55
+ CSS layer; then run the v22 migrations explicitly. The [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) details each step.
56
+
57
+ ```bash
58
+ npm install @exhaustive-ui/core@22
59
+ ng generate @exhaustive-ui/core:migrate-from-optimus
60
+ ng update @exhaustive-ui/core --migrate-only --from=3.0.0
61
+ ```
62
+
63
+ ### Then
64
+
65
+ 1. Read the report the migrations printed, see `Reviewing the report` below.
66
+ 2. Fix the TypeScript errors: most come from the Signals API and the removed TypeScript API.
67
+ 3. Check the screens that mutate data bound to a component, which no longer refresh under OnPush.
68
+ 4. Read the behavior changes, then build and run your tests.
69
+
70
+ ## Automated migrations
71
+
72
+ `ng update` applies nine migrations to the templates (inline and external) and the TypeScript code of every project in the workspace. Each one only touches the ExhaustiveUI elements and APIs it knows, and reports what it cannot
73
+ rewrite safely.
74
+
75
+ - **styleclass-to-class**: `styleClass`/`[styleClass]` becomes `class`/`[class]` on the ~60 components whose deprecated `styleClass` input was removed, such as Tag, Card, Select, Table, DatePicker, Panel, AvatarGroup and InputGroupAddon.
76
+ - **renamed-inputs**: Drawer `showCloseIcon` becomes `closable` and `ariaCloseLabel` becomes `closeAriaLabel`; Paginator `dropdownAppendTo` becomes `appendTo`; Password `maxLength` becomes `maxlength`; AutoComplete `minLength` becomes `minQueryLength`; TreeSelect `containerStyleClass`/`containerStyle` become `class`/`style`; TreeTable `virtualRowHeight` becomes `virtualScrollItemSize`; Listbox and MultiSelect `filterPlaceHolder` becomes `filterPlaceholder`; ImageCompare `ariaLabelledby` becomes `ariaLabelledBy`; Dialog `[content]`, which set the header template, becomes `[headerTemplate]`; the `pt*` pass-through aliases of pButton, pButtonLabel, pButtonIcon, pBadge, pInputText and pTooltip become `pButtonPT`, `pButtonLabelPT`, `pButtonIconPT`, `pBadgePT`, `pInputTextPT` and `pTooltipPT`; pBadge `size` on a plain element becomes `badgeSize`.
77
+ - **renamed-outputs**: OrderList `onFilterEvent` becomes `onFilter`; Table `selectAllChange` becomes `onSelectAllChange`; MultiSelect `onPanelShow`/`onPanelHide` become `onShow`/`onHide`. The payloads are unchanged, so handlers reading `$event` keep working.
78
+ - **renamed-templates**: the MultiSelect `removetokenicon` template becomes `chipicon`, with the same context.
79
+ - **remove-dead-inputs**: removes the bindings of about eighty inputs that had already stopped doing anything, such as the `*TransitionOptions` inputs (replaced by `motionOptions`), `autoZIndex`/`baseZIndex` on sub menus, Table `frozenColumns`/`frozenWidth`, the ConfirmDialog aria labels and the `trackBy` inputs of DataView, OrderList and PickList.
80
+ - **remove-dead-outputs**: removes Overlay `onAnimationStart`/`onAnimationDone` and MenubarSub `menuFocus`/`menuBlur`/`menuKeydown`.
81
+ - **config-overlay-options-signal**: `Exhaustive.overlayOptions` is a signal. Assignments become `.set()` and reads become calls.
82
+ - **config-input-style-to-variant**: the global `inputStyle` option becomes `inputVariant` (same values), in `provideExhaustive()`/`setConfig()` objects and on the `Exhaustive` service.
83
+ - **removed-exports**: `Password_VALUE_ACCESSOR` becomes `PASSWORD_VALUE_ACCESSOR`; the removed `InplaceDisplay`/`InplaceContent` wrappers are dropped from imports and their elements become `<span>`.
84
+
85
+ ## Reviewing the report
86
+
87
+ Each migration prints the files it changed, then the places it left for you, with the file and line. These are the cases it reports and what to do with them.
88
+
89
+ - **Programmatic access to a removed or renamed name**, such as `drawer.showCloseIcon = true` or `table.selectAllChange.subscribe(...)`: use the new name, and the Signals API described below.
90
+ - **A tag that binds both the old and the new name**: keep the new one and delete the old one, after checking which value you meant.
91
+ - **A Table `[(selectAll)]` two-way binding**, which relied on the renamed `selectAllChange`: bind `[selectAll]="selectAll"` and `(onSelectAllChange)="selectAll = $event.checked"`.
92
+ - **A MultiSelect that already projects a `chipicon` template** next to `removetokenicon`: keep one of them.
93
+ - **A configuration object that sets both `inputStyle` and `inputVariant` , or a receiver the migration cannot prove to be the `Exhaustive` service: set `inputVariant` only.
94
+ - Imports of rendering internals that are no longer exported**: the `SelectItem` option component of Select (the `SelectItem` interface of `@exhaustive-ui/core/api` is unchanged), Menu's `SafeHtmlPipe`, `MapperPipe`, `RadioControlRegistry` and `MenubarService`. Remove the import; the components no longer need them from you.
95
+
96
+ Coding agents can check the result with the `validate_usage` tool of the `@exhaustive-ui/mcp` server, which names the replacement of every input removed or renamed in v22, and follow its `update_to_v22` prompt.
97
+
98
+ ## Code using a component instance
99
+
100
+ Every input is an `input()`, every two-way property a `model()`, every output an `output()` and every query a signal query. No `@Input`, `@Output`, `@ViewChild` or
101
+ `@ContentChild` decorator is left. Templates are not affected, and the migrations do not rewrite this kind of code: the compiler points at each place.
102
+
103
+ - Read an input by calling it: `table.first()`, not `table.first`.
104
+ - Inputs can no longer be assigned from code. Bind them in the template to a field or a signal of your component, and change that instead.
105
+ - Two-way properties are `model()` signals: write them with `.set()`, as in `drawer.visible.set(true)`. The value and change-event pairs became models, for example `first`, `rows` and `selection` on Table and TreeTable, and `visible` on Dialog, Drawer and Galleria. `[(x)]` bindings keep working.
106
+ - Outputs are `OutputEmitterRef`s: `.subscribe()` still works, `.pipe()` and the other `EventEmitter` members do not. Use `outputToObservable()` when you need an observable.
107
+ - Public child references of a component are signal queries too, and are read with a call.
108
+ - The global configuration is a set of signals on the `Exhaustive` service: `config.ripple.set(true)`, `config.inputVariant()`.
109
+
110
+ ```typescript
111
+ // Before
112
+ @ViewChild(Table) table!: Table;
113
+ @ViewChild(Drawer) drawer!: Drawer;
114
+
115
+ reset() {
116
+ const first = this.table.first;
117
+ this.table.selection = [];
118
+ this.drawer.visible = false;
119
+ this.config.ripple = true;
120
+ }
121
+
122
+ // After
123
+ table = viewChild.required(Table);
124
+ drawer = viewChild.required(Drawer);
125
+
126
+ reset() {
127
+ const first = this.table().first();
128
+ this.table().selection.set([]);
129
+ this.drawer().visible.set(false);
130
+ this.config.ripple.set(true);
131
+ }
132
+ ```
133
+
134
+ ## OnPush change detection
135
+
136
+ Every component uses `OnPush` change detection, except Table, TreeTable and DynamicDialog, which stay Eager on purpose because they render objects that applications commonly mutate in place. An OnPush component refreshes when one
137
+ of its inputs gets a new value, when it handles an event, or when a signal it reads changes. It does not see a change made inside an array or an object it already holds.
138
+
139
+ The symptom is a component that does not update: options added with `push()` that do not appear in a Select, a Tree node renamed in place, a chart that keeps its old data. Give the component a new array or object, or keep the
140
+ data in a signal.
141
+
142
+ ```typescript
143
+ // Before: the Select does not show the new option under OnPush
144
+ this.cities.push({ name: 'Paris', code: 'PRS' });
145
+
146
+ // After: a new array
147
+ this.cities = [...this.cities, { name: 'Paris', code: 'PRS' }];
148
+
149
+ // Or a signal, bound with [options]="cities()"
150
+ cities = signal<City[]>([]);
151
+ this.cities.update((cities) => [...cities, { name: 'Paris', code: 'PRS' }]);
152
+ ```
153
+
154
+ Templates use the built-in `@if`, `@for` and `@switch` control flow, and option lists, menus, Paginator and DatePicker reuse their rows when the data is replaced instead of recreating them. Replacing the
155
+ array is therefore cheap, and no NG0955 or NG0956 warning comes from the library.
156
+
157
+ ## Removed TypeScript API
158
+
159
+ These removals have no migration: they only appear in TypeScript code, and the compiler points at each use.
160
+
161
+ - `OverlayOptions.showTransitionOptions`/`hideTransitionOptions` and `DynamicDialogConfig.rtl`/`transitionOptions`: nothing read them. Use `motionOptions`.
162
+ - `@exhaustive-ui/utils`: `classNames` becomes `cn`, `createStyleAsString` becomes `createStyleMarkup`, `createStyleTag` becomes `createStyleElement`, `mergeKeys` becomes `deepMerge`.
163
+ - `@exhaustive-ui/styled`: `getDirective` on the theme service becomes `getComponent`.
164
+ - Sub components that render the inside of a component (`ContextMenuSub`, `TieredMenuSub`, `MenuItemContent`, `MultiSelectItem`, `ToastItem`, `TableBody`, `TTBody`, `UITreeNode`, the Galleria parts...), `PARENT_INSTANCE` and the pre-signals helpers of `@exhaustive-ui/core/utils` are still exported in v22 but tagged `@internal`. They are not public API and can change in a minor release.
165
+
166
+ ## Behavior changes
167
+
168
+ These changes compile without error but can change what users see, or what a test asserts. Most come from fixes of bugs inherited from PrimeNG and Optimus UI. The issue numbers in the changelog are Optimus UI's.
169
+
170
+ ### Forms
171
+
172
+ - InputText: when `[invalid]` is bound, it alone decides the invalid style; the automatic `ng-invalid ng-dirty` border no longer applies on top of it.
173
+ - InputNumber: a keystroke that would make the formatted value longer than `maxlength` is rejected instead of truncating the text. The native `min`/`max` attributes are gone; the bounds stay in `aria-valuemin`/`aria-valuemax`.
174
+ - Select: a Select inside a disabled `<fieldset>` is disabled, except inside the fieldset's first `<legend>`, as for native controls.
175
+ - Select, MultiSelect and CascadeSelect use the SVG spinner of Button as their default loading icon, instead of the `pi-spin` icon class.
176
+ - PickList: moving items sets `source` and `target` to new arrays and emits `sourceChange`/`targetChange`, so `[(source)]`/`[(target)]` bindings follow.
177
+ - TreeTable: the selection change can fire once per intermediate step while a checkbox propagates.
178
+ - DatePicker: the `data-date` attribute of day cells uses a 1-based month.
179
+ - AutoFocus: the native `autofocus` attribute is only rendered when autofocus is on; Button and the other components no longer carry it by default.
180
+
181
+ ### Overlays and menus
182
+
183
+ - Overlays are placed against the viewport without its scrollbars, so an overlay at the right edge no longer goes under the vertical scrollbar.
184
+ - Tooltip honours the global `overlayAppendTo` option.
185
+ - TieredMenu: with `autoDisplay`, submenus open on hover from the start, without a first click. A popup TieredMenu gives the focus back to its trigger when an item is picked.
186
+ - ContextMenu: showing a context menu closes any other one that is open.
187
+ - ConfirmPopup: an `accepticon`/`rejecticon` template replaces the `acceptIcon`/`rejectIcon` class instead of rendering next to it, as in ConfirmDialog.
188
+
189
+ ### Accessibility markup
190
+
191
+ - Stepper: the `tablist` role is on `p-step-list`. Splitter: the `separator` role is on the focusable gutter handle.
192
+ - FocusTrap sentinels are no longer `aria-hidden`. ConfirmDialog no longer puts a `role` on the `p-dialog` host.
193
+ - Table announces keyboard column and row moves through the new `aria.columnMoved` and `aria.rowMoved` translation keys. A custom `aria` translation without them falls back to English.
194
+
195
+ ### Theming and display
196
+
197
+ - A token overridden under `colorScheme.light` wins over the preset's top-level token, as it already did in dark mode. A top-level override passed to `definePreset`, `updatePreset` or `usePreset` still wins.
198
+ - MeterGroup: meter widths use the exact percentage; labels keep the rounded value.
199
+ - ToggleSwitch has no `size` input any more: it had no effect.
200
+
201
+ ## Type changes
202
+
203
+ Some types now describe what the components actually emit or accept. Code that relied on the old types may need a cast or a narrower check.
204
+
205
+ - Table `onFilter`: `filters` is typed `FilterMetadata | FilterMetadata[]`.
206
+ - TreeTable `TreeTableLazyLoadEvent`: `first` is a `number` and `last` an optional `number`, as in `TableLazyLoadEvent`.
207
+ - CascadeSelect: `options` is typed as an array, and the value accepts an object.
208
+ - Dialog and ConfirmDialog: `pt.root` is typed as the options of the root element.
209
+ - Chart `onDataSelect` emits the new exported `ChartDataSelectEvent` type.
210
+ - `Confirmation` accepts `draggable`, and DatePicker `hourFormat` also accepts a number.
211
+
212
+ ## Checklist
213
+
214
+ - Angular 22 installed, and `ng update` (or `--migrate-only --from=3.0.0`) run on a clean working tree.
215
+ - Every place listed in the migration report handled.
216
+ - The project compiles: inputs are read with a call, two-way properties written with `.set()`, removed TypeScript API replaced.
217
+ - No `styleClass`, removed input or `pt*` alias left in templates: `validate_usage` of the MCP server can check this.
218
+ - Screens that change data bound to a component show the change: new arrays and objects, or signals, rather than in-place mutation.
219
+ - Behavior changes reviewed against your tests and screenshots.
220
+ - Signal Forms, if you adopt them: a required field shows as invalid before any interaction, because `[invalid]` cannot be bound next to `[formField]`. A fix is planned in a v22 minor release.
221
+
@@ -1,9 +1,9 @@
1
1
  {
2
- "generatedAt": "2026-11-22T01:07:27.323Z",
3
- "libraryVersion": "22.0.0-rc.3",
2
+ "generatedAt": "2026-11-22T11:45:07.223Z",
3
+ "libraryVersion": "22.0.1",
4
4
  "docsGeneratedAt": "2026-11-22",
5
5
  "components": 96,
6
- "guides": 17,
6
+ "guides": 20,
7
7
  "source": "local",
8
8
  "origin": "../../apps/docs/public/llms"
9
9
  }
package/dist/index.mjs CHANGED
@@ -2679,8 +2679,8 @@ const PROMPTS = {
2679
2679
  title: "Migrate from PrimeNG",
2680
2680
  description: "Plan the migration of PrimeNG (or Optimus UI) code to ExhaustiveUI.",
2681
2681
  steps: [
2682
- "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`.",
2683
- "Call get_guide for \"faq\" (migration notes) and get_setup for \"angular-cli\".",
2682
+ "Call get_guide for \"primeng\" (from PrimeNG v21) or \"optimus\" (from Optimus UI v2), and follow its steps.",
2683
+ "From PrimeNG: update Angular to v22 with --force while primeng is installed, then run `ng generate @exhaustive-ui/core:migrate-from-primeng`. From Optimus UI: run `ng generate @exhaustive-ui/core:migrate-from-optimus`. Then run `ng update @exhaustive-ui/core --migrate-only --from=3.0.0` and follow get_guide \"v22\".",
2684
2684
  "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.",
2685
2685
  "Replace `primeng/<name>` imports with `@exhaustive-ui/core/<name>` and call validate_usage on each migrated template."
2686
2686
  ]
@@ -2689,8 +2689,8 @@ const PROMPTS = {
2689
2689
  title: "Update to ExhaustiveUI v22",
2690
2690
  description: "Update an application to ExhaustiveUI v22 (Angular v22, Signals API) and fix what ng update leaves for review.",
2691
2691
  steps: [
2692
- "Call get_guide for \"update\" and read its v22 section.",
2693
- "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.",
2692
+ "Call get_guide for \"v22\" (the migration guide to v22) and follow its update steps for the starting point: an ExhaustiveUI prerelease, PrimeNG v21 or Optimus UI.",
2693
+ "Update Angular first (`ng update @angular/core@22 @angular/cli@22`), then run `ng update @exhaustive-ui/core@22`; its nine migrations rewrite styleClass to class, renamed inputs, outputs and templates, bindings of removed inputs and outputs, and the configuration API, and print what they left for review. Handle each reported place as the \"Reviewing the report\" section of the guide describes.",
2694
2694
  "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.",
2695
2695
  "Components are OnPush (except Table, TreeTable and DynamicDialog): pass new arrays or objects, or signals, instead of mutating data bound to them in place.",
2696
2696
  "Call validate_usage on each template that uses a `p-*` element: removed or renamed v22 inputs are reported with their replacement."