@exhaustive-ui/mcp 22.0.0-alpha.2 → 22.0.0-alpha.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/data/components.json +2 -2
- package/data/llms-full.txt +2 -2
- package/data/manifest.json +3 -3
- package/data/pages/faq.md +1 -1
- package/data/pages/installation.md +1 -1
- package/data/snapshot.json +2 -2
- package/package.json +1 -1
package/data/components.json
CHANGED
|
@@ -42902,7 +42902,7 @@
|
|
|
42902
42902
|
{
|
|
42903
42903
|
"id": "prerequisites-",
|
|
42904
42904
|
"label": "Prerequisites-",
|
|
42905
|
-
"description": "ExhaustiveUI targets Angular
|
|
42905
|
+
"description": "ExhaustiveUI v22 targets Angular v22. Any workspace created with the Angular CLI works, standalone or NgModule based. Angular v22, including @angular/cdk , @angular/forms and @angular/router RxJS v7.8.1 or newer A package manager of your choice — npm, yarn or pnpm Already using PrimeNG? Do not follow this page. The migration guide covers moving an existing PrimeNG v21 workspace, once updated to Angular v22, across with the migrate-from-primeng schematic, which is a separate command from the ng add below.",
|
|
42906
42906
|
"examples": null
|
|
42907
42907
|
},
|
|
42908
42908
|
{
|
|
@@ -43698,7 +43698,7 @@
|
|
|
43698
43698
|
{
|
|
43699
43699
|
"id": "migration-",
|
|
43700
43700
|
"label": "Migration-",
|
|
43701
|
-
"description": "Which Angular versions are supported? Angular
|
|
43701
|
+
"description": "Which Angular versions are supported? Angular v22: ExhaustiveUI v22 requires Angular v22. Our majors follow Angular's — when a new Angular major ships, a compatible ExhaustiveUI major is the first thing we work on. See the version compatibility table in the update guide. How do I migrate from PrimeNG? Is it automatic? Mostly, but not through ng add , which only sets up new projects and fails without changing anything when it finds an existing primeng dependency. Install @exhaustive-ui/core , then run ng generate @exhaustive-ui/core:migrate-from-primeng in a PrimeNG v21 workspace updated to Angular v22: packages swapped, imports rewritten, dependencies installed. It then prints a report of anything it could not rewrite, with file and line numbers. The migration guide covers the details and the manual cases. I am on PrimeNG v20 or older. Can I migrate directly? No. Upgrade to PrimeNG v21 first, using PrimeNG's own migration guides, then update Angular to v22 and run the schematic. The schematic checks the version and refuses rather than producing a half-migrated workspace. What happens to my PrimeNG license? Nothing — it is unrelated. A PrimeNG v22 commercial license covers PrimeNG. ExhaustiveUI needs no license at all. If you hold a PrimeTek subscription for their templates or theme designer, those remain their products and do not carry over here. I had an open PR on primefaces/primeng. Can I bring it here? Yes, and we would like you to. Append .patch to your original pull request URL and apply it with git am — the contributing guide in the repository walks through it, including what to do when the patch no longer applies cleanly. Can I run PrimeNG and ExhaustiveUI side by side? Technically yes, since the package names and the CSS cascade layer differ, but you will ship two copies of the same components and two theme runtimes. Treat it as a temporary state during migration rather than a supported configuration.",
|
|
43702
43702
|
"examples": null
|
|
43703
43703
|
},
|
|
43704
43704
|
{
|
package/data/llms-full.txt
CHANGED
|
@@ -32,7 +32,7 @@ The recommended way to add ExhaustiveUI to an Angular CLI workspace is a single
|
|
|
32
32
|
|
|
33
33
|
## Prerequisites-
|
|
34
34
|
|
|
35
|
-
ExhaustiveUI targets Angular
|
|
35
|
+
ExhaustiveUI v22 targets Angular v22. Any workspace created with the Angular CLI works, standalone or NgModule based. Angular v22, including @angular/cdk , @angular/forms and @angular/router RxJS v7.8.1 or newer A package manager of your choice — npm, yarn or pnpm Already using PrimeNG? Do not follow this page. The migration guide covers moving an existing PrimeNG v21 workspace, once updated to Angular v22, across with the migrate-from-primeng schematic, which is a separate command from the ng add below.
|
|
36
36
|
|
|
37
37
|
## Provider-
|
|
38
38
|
|
|
@@ -805,7 +805,7 @@ Do the PrimeNG themes work? The built-in presets do — Aura, Material, Lara and
|
|
|
805
805
|
|
|
806
806
|
## Migration-
|
|
807
807
|
|
|
808
|
-
Which Angular versions are supported? Angular
|
|
808
|
+
Which Angular versions are supported? Angular v22: ExhaustiveUI v22 requires Angular v22. Our majors follow Angular's — when a new Angular major ships, a compatible ExhaustiveUI major is the first thing we work on. See the version compatibility table in the update guide. How do I migrate from PrimeNG? Is it automatic? Mostly, but not through ng add , which only sets up new projects and fails without changing anything when it finds an existing primeng dependency. Install @exhaustive-ui/core , then run ng generate @exhaustive-ui/core:migrate-from-primeng in a PrimeNG v21 workspace updated to Angular v22: packages swapped, imports rewritten, dependencies installed. It then prints a report of anything it could not rewrite, with file and line numbers. The migration guide covers the details and the manual cases. I am on PrimeNG v20 or older. Can I migrate directly? No. Upgrade to PrimeNG v21 first, using PrimeNG's own migration guides, then update Angular to v22 and run the schematic. The schematic checks the version and refuses rather than producing a half-migrated workspace. What happens to my PrimeNG license? Nothing — it is unrelated. A PrimeNG v22 commercial license covers PrimeNG. ExhaustiveUI needs no license at all. If you hold a PrimeTek subscription for their templates or theme designer, those remain their products and do not carry over here. I had an open PR on primefaces/primeng. Can I bring it here? Yes, and we would like you to. Append .patch to your original pull request URL and apply it with git am — the contributing guide in the repository walks through it, including what to do when the patch no longer applies cleanly. Can I run PrimeNG and ExhaustiveUI side by side? Technically yes, since the package names and the CSS cascade layer differ, but you will ship two copies of the same components and two theme runtimes. Treat it as a temporary state during migration rather than a supported configuration.
|
|
809
809
|
|
|
810
810
|
## Project-
|
|
811
811
|
|
package/data/manifest.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
3
|
"package": "@exhaustive-ui/core",
|
|
4
|
-
"version": "22.0.0-alpha.
|
|
4
|
+
"version": "22.0.0-alpha.3",
|
|
5
5
|
"site": "https://exhaustive-ui.com",
|
|
6
6
|
"entryPoints": [
|
|
7
7
|
{
|
|
@@ -13388,7 +13388,7 @@
|
|
|
13388
13388
|
"kind": "property",
|
|
13389
13389
|
"type": "boolean | undefined",
|
|
13390
13390
|
"description": "Inline style of the component.",
|
|
13391
|
-
"deprecated": "since
|
|
13391
|
+
"deprecated": "since v22.0.0. It has no effect anymore: the dialog never read it."
|
|
13392
13392
|
},
|
|
13393
13393
|
{
|
|
13394
13394
|
"name": "style",
|
|
@@ -13413,7 +13413,7 @@
|
|
|
13413
13413
|
"kind": "property",
|
|
13414
13414
|
"type": "string | undefined",
|
|
13415
13415
|
"description": "Transition options of the animation.",
|
|
13416
|
-
"deprecated": "since
|
|
13416
|
+
"deprecated": "since v22.0.0. It has no effect anymore: the dialog animation is driven by motion options."
|
|
13417
13417
|
},
|
|
13418
13418
|
{
|
|
13419
13419
|
"name": "closable",
|
package/data/pages/faq.md
CHANGED
|
@@ -8,7 +8,7 @@ Do the PrimeNG themes work? The built-in presets do — Aura, Material, Lara and
|
|
|
8
8
|
|
|
9
9
|
## Migration-
|
|
10
10
|
|
|
11
|
-
Which Angular versions are supported? Angular
|
|
11
|
+
Which Angular versions are supported? Angular v22: ExhaustiveUI v22 requires Angular v22. Our majors follow Angular's — when a new Angular major ships, a compatible ExhaustiveUI major is the first thing we work on. See the version compatibility table in the update guide. How do I migrate from PrimeNG? Is it automatic? Mostly, but not through ng add , which only sets up new projects and fails without changing anything when it finds an existing primeng dependency. Install @exhaustive-ui/core , then run ng generate @exhaustive-ui/core:migrate-from-primeng in a PrimeNG v21 workspace updated to Angular v22: packages swapped, imports rewritten, dependencies installed. It then prints a report of anything it could not rewrite, with file and line numbers. The migration guide covers the details and the manual cases. I am on PrimeNG v20 or older. Can I migrate directly? No. Upgrade to PrimeNG v21 first, using PrimeNG's own migration guides, then update Angular to v22 and run the schematic. The schematic checks the version and refuses rather than producing a half-migrated workspace. What happens to my PrimeNG license? Nothing — it is unrelated. A PrimeNG v22 commercial license covers PrimeNG. ExhaustiveUI needs no license at all. If you hold a PrimeTek subscription for their templates or theme designer, those remain their products and do not carry over here. I had an open PR on primefaces/primeng. Can I bring it here? Yes, and we would like you to. Append .patch to your original pull request URL and apply it with git am — the contributing guide in the repository walks through it, including what to do when the patch no longer applies cleanly. Can I run PrimeNG and ExhaustiveUI side by side? Technically yes, since the package names and the CSS cascade layer differ, but you will ship two copies of the same components and two theme runtimes. Treat it as a temporary state during migration rather than a supported configuration.
|
|
12
12
|
|
|
13
13
|
## Project-
|
|
14
14
|
|
|
@@ -39,7 +39,7 @@ ng add @exhaustive-ui/core
|
|
|
39
39
|
|
|
40
40
|
## Prerequisites-
|
|
41
41
|
|
|
42
|
-
ExhaustiveUI targets Angular
|
|
42
|
+
ExhaustiveUI v22 targets Angular v22. Any workspace created with the Angular CLI works, standalone or NgModule based. Angular v22, including @angular/cdk , @angular/forms and @angular/router RxJS v7.8.1 or newer A package manager of your choice — npm, yarn or pnpm Already using PrimeNG? Do not follow this page. The migration guide covers moving an existing PrimeNG v21 workspace, once updated to Angular v22, across with the migrate-from-primeng schematic, which is a separate command from the ng add below.
|
|
43
43
|
|
|
44
44
|
## Provider-
|
|
45
45
|
|
package/data/snapshot.json
CHANGED