@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.
@@ -43692,63 +43692,59 @@
43692
43692
  "description": "Setting up ExhaustiveUI in an Angular CLI project.",
43693
43693
  "sections": [
43694
43694
  {
43695
- "id": "download",
43696
- "label": "Download",
43697
- "description": "Prefer to wire things up yourself? Install the packages from the npm registry directly. The next section covers the provider setup that ng add would have written for you.",
43698
- "examples": {
43699
- "command": "# Using npm\nnpm install @exhaustive-ui/core @exhaustive-ui/themes\n\n# Using yarn\nyarn add @exhaustive-ui/core @exhaustive-ui/themes\n\n# Using pnpm\npnpm add @exhaustive-ui/core @exhaustive-ui/themes"
43700
- }
43701
- },
43702
- {
43703
- "id": "examples",
43704
- "label": "Examples",
43705
- "description": "Every example in this documentation opens in StackBlitz from the code toolbar above each demo, already wired up with the current version. The source repository is the reference for how the library itself is built and consumed.",
43695
+ "id": "prerequisites",
43696
+ "label": "Prerequisites",
43697
+ "description": "ExhaustiveUI v22 targets Angular v22. Any workspace created with the Angular CLI works, standalone or NgModule based.\n\n- Angular v22, including `@angular/cdk`, `@angular/forms` and `@angular/router`; the form components work with template-driven forms, reactive forms and Signal Forms (`@angular/forms/signals`)\n- RxJS v7.8.1 or newer\n- A package manager of your choice — npm, yarn or pnpm\n\nAlready using PrimeNG? Do not follow this page. The [migration guide](https://exhaustive-ui.com/migration/primeng) covers moving an existing PrimeNG v21 workspace, once updated to Angular v22, across with the\n`migrate-from-primeng` schematic, which is a separate command from the `ng add` below. On Optimus UI v2, follow the [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) and its\n`migrate-from-optimus` schematic instead.",
43706
43698
  "examples": null
43707
43699
  },
43708
43700
  {
43709
- "id": "icons",
43710
- "label": "Icons",
43711
- "description": "ExhaustiveUI components accept any icon through templating, so an icon library is optional. That said, every example in this documentation uses the pi pi-{icon} classes from OpenNG Icons , and component defaults such as the DatePicker arrows reference them too. Install it if you want the demos to look the way they do here. Then import the stylesheet, either from your global stylesheet or from the styles array in angular.json .",
43701
+ "id": "compatibility",
43702
+ "label": "Angular Version Compatibility",
43703
+ "description": "Each ExhaustiveUI major targets a single Angular major. Install the version matching your workspace, and see the [update guide](https://exhaustive-ui.com/migration/update) when moving to a newer one.",
43712
43704
  "examples": null
43713
43705
  },
43714
43706
  {
43715
- "id": "nextsteps",
43716
- "label": "Nextsteps",
43717
- "description": "Once you have ExhaustiveUI up and running, we recommend exploring the following resources to gain a deeper understanding of the library. Global configuration Styled mode and unstyled mode Tailwind CSS integration Pass Through for direct access to the underlying elements Philosophy — what this project promises, and what it does not FAQ",
43707
+ "id": "ngadd",
43708
+ "label": "Install",
43709
+ "description": "The recommended way to add ExhaustiveUI to an Angular CLI workspace is a single command.\n\n```bash\nng add @exhaustive-ui/core\n```\n\nThe schematic asks which theme preset you want and then does the rest:\n\n- adds `@exhaustive-ui/core` and `@exhaustive-ui/themes` to your dependencies\n- wires `provideExhaustive` into your root providers with the chosen preset, in `app.config.ts` or your root NgModule\n- installs the packages\n\nPass the preset up front to skip the prompt, or skip the install step if you want to run it yourself:\n\n```bash\n# Choose the preset without the prompt — Aura, Lara, Material or Nora\nng add @exhaustive-ui/core --theme=Lara\n\n# Wire everything up but do not run the package install\nng add @exhaustive-ui/core --skip-install\n\n# Target a specific project in a multi-project workspace\nng add @exhaustive-ui/core --project=admin\n```\n\nIf the schematic cannot find a providers array to update it prints the three manual steps instead of guessing, so nothing in your workspace is rewritten unexpectedly. If it detects an existing `primeng` or\n`@openng/optimus-ui` dependency it changes nothing and fails with an error rather than reporting success, and points you at the `migrate-from-primeng` or `migrate-from-optimus` schematic, described in the\n[PrimeNG](https://exhaustive-ui.com/migration/primeng) and [Optimus UI](https://exhaustive-ui.com/migration/optimus) migration guides. It does not run that schematic for you. The Angular CLI installs\n`@exhaustive-ui/core` before the schematic runs, so the dependency stays in your `package.json` — the migration schematic needs it there.",
43718
43710
  "examples": null
43719
43711
  },
43720
43712
  {
43721
- "id": "ngadd",
43722
- "label": "Ngadd",
43723
- "description": "The recommended way to add ExhaustiveUI to an Angular CLI workspace is a single command. The schematic asks which theme preset you want and then does the rest: adds @exhaustive-ui/core and @exhaustive-ui/themes to your dependencies wires provideExhaustive into your root providers with the chosen preset, in app.config.ts or your root NgModule installs the packages Pass the preset up front to skip the prompt, or skip the install step if you want to run it yourself: If the schematic cannot find a providers array to update it prints the three manual steps instead of guessing, so nothing in your workspace is rewritten unexpectedly. If it detects an existing primeng dependency it changes nothing and fails with an error rather than reporting success, and points you at the migration guide , which covers the migrate-from-primeng schematic. It does not run that schematic for you. The Angular CLI installs @exhaustive-ui/core before the schematic runs, so the dependency stays in your package.json — the migration schematic needs it there.",
43713
+ "id": "download",
43714
+ "label": "Download",
43715
+ "description": "Prefer to wire things up yourself? Install the packages from the [npm registry](https://www.npmjs.com/package/@exhaustive-ui/core) directly. The next section covers the provider\nsetup that `ng add` would have written for you.",
43724
43716
  "examples": {
43725
- "command": "ng add @exhaustive-ui/core"
43717
+ "command": "# Using npm\nnpm install @exhaustive-ui/core @exhaustive-ui/themes\n\n# Using yarn\nyarn add @exhaustive-ui/core @exhaustive-ui/themes\n\n# Using pnpm\npnpm add @exhaustive-ui/core @exhaustive-ui/themes"
43726
43718
  }
43727
43719
  },
43728
43720
  {
43729
- "id": "prerequisites",
43730
- "label": "Prerequisites",
43731
- "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 ; the form components work with template-driven forms, reactive forms and Signal Forms ( @angular/forms/signals ) 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.",
43721
+ "id": "provider",
43722
+ "label": "Provider",
43723
+ "description": "Add `provideExhaustive` to the list of providers in your `app.config.ts` and use the `theme` property to configure a theme such as Aura.\n\n```typescript\nimport { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n theme: {\n preset: Aura\n }\n })\n ]\n};\n```",
43732
43724
  "examples": null
43733
43725
  },
43734
43726
  {
43735
- "id": "provider",
43736
- "label": "Provider",
43737
- "description": "Add provideExhaustive to the list of providers in your app.config.ts and use the theme property to configure a theme such as Aura.",
43738
- "examples": {
43739
- "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n theme: {\n preset: Aura\n }\n })\n ]\n};"
43740
- }
43727
+ "id": "icons",
43728
+ "label": "Icons",
43729
+ "description": "ExhaustiveUI components accept any icon through templating, so an icon library is optional. That said, every example in this documentation uses the `pi pi-{icon}` classes from\n[OpenNG Icons](https://exhaustive-ui.com/icons), and component defaults such as the DatePicker arrows reference them too. Install it if you want the demos to look the way they do here.\n\n```bash\nnpm install @openng/icons\n```\n\nThen import the stylesheet, either from your global stylesheet or from the `styles` array in `angular.json`.\n\n```scss\n@import \"@openng/icons/openng-icons.css\";\n```",
43730
+ "examples": null
43741
43731
  },
43742
43732
  {
43743
43733
  "id": "verify",
43744
43734
  "label": "Verify",
43745
- "description": "Verify your setup by adding a component such as Button. Each component can be imported and registered individually so that you only include what you use for bundle optimization. Import path is available in the documentation of the corresponding component.",
43735
+ "description": "Verify your setup by adding a component such as Button. Each component can be imported and registered individually so that you only include what you use for bundle optimization. Import path is available in the documentation of the\ncorresponding component.",
43736
+ "examples": null
43737
+ },
43738
+ {
43739
+ "id": "examples",
43740
+ "label": "Examples",
43741
+ "description": "Every example in this documentation opens in StackBlitz from the code toolbar above each demo, already wired up with the current version. The\n[source repository](https://github.com/e-xiste/exhaustive-ui) is the reference for how the library itself is built and consumed.",
43746
43742
  "examples": null
43747
43743
  },
43748
43744
  {
43749
- "id": "versioncompatibility",
43750
- "label": "Versioncompatibility",
43751
- "description": "Each ExhaustiveUI major targets a single Angular major. Install the version matching your workspace, and see the update guide when moving to a newer one.",
43745
+ "id": "nextsteps",
43746
+ "label": "Next Steps",
43747
+ "description": "Once you have ExhaustiveUI up and running, we recommend exploring the following resources to gain a deeper understanding of the library.\n\n- [Global configuration](https://exhaustive-ui.com/configuration)\n- [Styled mode](https://exhaustive-ui.com/theming/styled) and [unstyled mode](https://exhaustive-ui.com/theming/unstyled)\n- [Tailwind CSS integration](https://exhaustive-ui.com/tailwind)\n- [Pass Through](https://exhaustive-ui.com/passthrough) for direct access to the underlying elements\n- [Philosophy](https://exhaustive-ui.com/philosophy) — what this project promises, and what it does not\n- [FAQ](https://exhaustive-ui.com/faq)",
43752
43748
  "examples": null
43753
43749
  }
43754
43750
  ]
@@ -43760,102 +43756,98 @@
43760
43756
  "description": "Application wide configuration for ExhaustiveUI.",
43761
43757
  "sections": [
43762
43758
  {
43763
- "id": "csp",
43764
- "label": "Csp",
43765
- "description": "The nonce value to use on dynamically generated style elements in core.",
43759
+ "id": "provider",
43760
+ "label": "Provider",
43761
+ "description": "The initial configuration is defined by the `provideExhaustive` provider during application startup.",
43766
43762
  "examples": {
43767
- "typescript": "provideExhaustive({\n csp: {\n nonce: '...'\n }\n})"
43763
+ "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({ /* options */ })\n ]\n};"
43768
43764
  }
43769
43765
  },
43770
43766
  {
43771
43767
  "id": "dynamic",
43772
43768
  "label": "Dynamic",
43773
- "description": "Inject the Exhaustive to your application to update the initial configuration at runtime.",
43769
+ "description": "Inject the `Exhaustive` to your application to update the initial configuration at runtime.",
43774
43770
  "examples": {
43775
43771
  "typescript": "import { Component, OnInit } from '@angular/core';\nimport { Exhaustive } from '@exhaustive-ui/core/config';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private config: Exhaustive) {}\n\n ngOnInit() {\n this.config.ripple.set(true);\n }\n}"
43776
43772
  }
43777
43773
  },
43778
43774
  {
43779
- "id": "filtermode",
43780
- "label": "Filtermode",
43781
- "description": "Default filter modes to display on DataTable filter menus.",
43775
+ "id": "theme",
43776
+ "label": "Theme",
43777
+ "description": "ExhaustiveUI provides 4 predefined themes out of the box; Aura, Material, Lara and Nora. See the theming documentation for details.",
43782
43778
  "examples": {
43783
- "typescript": "import { ExhaustiveConfig } from '@exhaustive-ui/core/api';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private exhaustiveConfig: ExhaustiveConfig) {}\n\n ngOnInit() {\n exhaustiveConfig.filterMatchModeOptions = {\n text: [FilterMatchMode.STARTS_WITH, FilterMatchMode.CONTAINS, FilterMatchMode.NOT_CONTAINS, FilterMatchMode.ENDS_WITH, FilterMatchMode.EQUALS, FilterMatchMode.NOT_EQUALS],\n numeric: [FilterMatchMode.EQUALS, FilterMatchMode.NOT_EQUALS, FilterMatchMode.LESS_THAN, FilterMatchMode.LESS_THAN_OR_EQUAL_TO, FilterMatchMode.GREATER_THAN, FilterMatchMode.GREATER_THAN_OR_EQUAL_TO],\n date: [FilterMatchMode.DATE_IS, FilterMatchMode.DATE_IS_NOT, FilterMatchMode.DATE_BEFORE, FilterMatchMode.DATE_AFTER]\n };\n }\n}"
43779
+ "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\n\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n theme: {\n preset: Aura,\n options: {\n prefix: 'p',\n darkModeSelector: 'system',\n cssLayer: false\n }\n }\n })\n ]\n};"
43780
+ }
43781
+ },
43782
+ {
43783
+ "id": "ripple",
43784
+ "label": "Ripple",
43785
+ "description": "Ripple is an optional animation for the supported components such as buttons. It is disabled by default.",
43786
+ "examples": {
43787
+ "typescript": "provideExhaustive({\n ripple: true\n})"
43784
43788
  }
43785
43789
  },
43786
43790
  {
43787
43791
  "id": "inputvariant",
43788
- "label": "Inputvariant",
43789
- "description": "Input fields come in two styles, default is outlined with borders around the field whereas filled alternative adds a background color to the field. A theme such as Material may add more additional design changes per each variant.",
43792
+ "label": "InputVariant",
43793
+ "description": "Input fields come in two styles, default is `outlined` with borders around the field whereas `filled` alternative adds a background color to the field. A theme such as Material may add more additional design changes per each\nvariant.",
43790
43794
  "examples": null
43791
43795
  },
43792
43796
  {
43793
- "id": "locale/api",
43794
- "label": "Api",
43795
- "description": "Locale Options",
43797
+ "id": "overlayappendto",
43798
+ "label": "OverlayAppendTo",
43799
+ "description": "Defines the default location of the overlays; `self` refers to the host element and `body` targets the document body. Defaults to `self`.",
43796
43800
  "examples": null
43797
43801
  },
43798
43802
  {
43799
- "id": "locale/repository",
43800
- "label": "Repository",
43801
- "description": "Ready to use settings for locales are available as the @exhaustive-ui/locale package, maintained in the ExhaustiveUI repository. We'd appreciate if you could contribute translations to the repository and share them with the rest of the community.",
43803
+ "id": "zIndex",
43804
+ "label": "ZIndex",
43805
+ "description": "ZIndexes are managed automatically to make sure layering of overlay components work seamlessly when combining multiple components. Still there may be cases where you'd like to configure the configure default values such as a custom\nlayout where header section is fixed. In a case like this, dropdown needs to be displayed below the application header but a modal dialog should be displayed above. ExhaustiveUI configuration offers the `zIndex` property to\ncustomize the default values for components categories. Default values are described below and can be customized when setting up ExhaustiveUI.",
43802
43806
  "examples": {
43803
- "typescript": "import { de } from '@exhaustive-ui/locale/js/de.js';\n\nprovideExhaustive({\n translation: de\n})"
43807
+ "typescript": "import { ExhaustiveConfig } from '@exhaustive-ui/core/api';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private exhaustiveConfig: ExhaustiveConfig) {}\n\n ngOnInit() {\n this.exhaustiveConfig.zIndex = {\n modal: 1100, // dialog, sidebar\n overlay: 1000, // dropdown, overlaypanel\n menu: 1000, // overlay menus\n tooltip: 1100 // tooltip\n };\n }\n}"
43804
43808
  }
43805
43809
  },
43806
43810
  {
43807
- "id": "locale/runtime",
43808
- "label": "Runtime",
43809
- "description": "The translations can be changed dynamically at runtime, here is an example with ngx-translate.",
43811
+ "id": "csp-nonce",
43812
+ "label": "Nonce",
43813
+ "description": "The `nonce` value to use on dynamically generated style elements in core.",
43810
43814
  "examples": {
43811
- "typescript": "import { Component, OnInit } from '@angular/core';\nimport { Exhaustive } from '@exhaustive-ui/core/config';\nimport { TranslateService } from '@ngx-translate/core';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private config: Exhaustive, private translateService: TranslateService) {}\n\n ngOnInit() {\n this.translateService.setDefaultLang('en');\n }\n\n translate(lang: string) {\n this.translateService.use(lang);\n this.translateService.get('exhaustive').subscribe(res => this.config.setTranslation(res));\n }\n}"
43815
+ "typescript": "provideExhaustive({\n csp: {\n nonce: '...'\n }\n})"
43812
43816
  }
43813
43817
  },
43814
43818
  {
43815
- "id": "locale/translation",
43816
- "label": "Translation",
43817
- "description": "A translation is specified using the translation property during initialization.",
43819
+ "id": "filter-mode",
43820
+ "label": "Filter Mode",
43821
+ "description": "Default filter modes to display on DataTable filter menus.",
43818
43822
  "examples": {
43819
- "typescript": "provideExhaustive({\n translation: {\n accept: 'Aceptar',\n reject: 'Rechazar',\n //translations\n }\n})"
43823
+ "typescript": "import { ExhaustiveConfig } from '@exhaustive-ui/core/api';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private exhaustiveConfig: ExhaustiveConfig) {}\n\n ngOnInit() {\n exhaustiveConfig.filterMatchModeOptions = {\n text: [FilterMatchMode.STARTS_WITH, FilterMatchMode.CONTAINS, FilterMatchMode.NOT_CONTAINS, FilterMatchMode.ENDS_WITH, FilterMatchMode.EQUALS, FilterMatchMode.NOT_EQUALS],\n numeric: [FilterMatchMode.EQUALS, FilterMatchMode.NOT_EQUALS, FilterMatchMode.LESS_THAN, FilterMatchMode.LESS_THAN_OR_EQUAL_TO, FilterMatchMode.GREATER_THAN, FilterMatchMode.GREATER_THAN_OR_EQUAL_TO],\n date: [FilterMatchMode.DATE_IS, FilterMatchMode.DATE_IS_NOT, FilterMatchMode.DATE_BEFORE, FilterMatchMode.DATE_AFTER]\n };\n }\n}"
43820
43824
  }
43821
43825
  },
43822
43826
  {
43823
- "id": "overlayappendto",
43824
- "label": "Overlayappendto",
43825
- "description": "Defines the default location of the overlays; self refers to the host element and body targets the document body. Defaults to self .",
43827
+ "id": "translation",
43828
+ "label": "Translation",
43829
+ "description": "A translation is specified using the translation property during initialization.\n\n```typescript\nprovideExhaustive({\n translation: {\n accept: 'Aceptar',\n reject: 'Rechazar',\n //translations\n }\n})\n```",
43826
43830
  "examples": null
43827
43831
  },
43828
43832
  {
43829
- "id": "provider",
43830
- "label": "Provider",
43831
- "description": "The initial configuration is defined by the provideExhaustive provider during application startup.",
43832
- "examples": {
43833
- "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({ /* options */ })\n ]\n};"
43834
- }
43835
- },
43836
- {
43837
- "id": "ripple",
43838
- "label": "Ripple",
43839
- "description": "Ripple is an optional animation for the supported components such as buttons. It is disabled by default.",
43833
+ "id": "Runtime",
43834
+ "label": "Runtime",
43835
+ "description": "The translations can be changed dynamically at runtime, here is an example with ngx-translate.",
43840
43836
  "examples": {
43841
- "typescript": "provideExhaustive({\n ripple: true\n})"
43837
+ "typescript": "import { Component, OnInit } from '@angular/core';\nimport { Exhaustive } from '@exhaustive-ui/core/config';\nimport { TranslateService } from '@ngx-translate/core';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private config: Exhaustive, private translateService: TranslateService) {}\n\n ngOnInit() {\n this.translateService.setDefaultLang('en');\n }\n\n translate(lang: string) {\n this.translateService.use(lang);\n this.translateService.get('exhaustive').subscribe(res => this.config.setTranslation(res));\n }\n}"
43842
43838
  }
43843
43839
  },
43844
43840
  {
43845
- "id": "theme",
43846
- "label": "Theme",
43847
- "description": "ExhaustiveUI provides 4 predefined themes out of the box; Aura, Material, Lara and Nora. See the theming documentation for details.",
43848
- "examples": {
43849
- "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\n\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n theme: {\n preset: Aura,\n options: {\n prefix: 'p',\n darkModeSelector: 'system',\n cssLayer: false\n }\n }\n })\n ]\n};"
43850
- }
43841
+ "id": "repository",
43842
+ "label": "Repository",
43843
+ "description": "Ready to use settings for locales are available as the `@exhaustive-ui/locale` package, maintained in the\n[ExhaustiveUI](https://github.com/e-xiste/exhaustive-ui/tree/main/packages/locale) repository. We'd appreciate if you could contribute translations to the repository and share them\nwith the rest of the community.\n\n```typescript\nimport { de } from '@exhaustive-ui/locale/js/de.js';\n\nprovideExhaustive({\n translation: de\n})\n```",
43844
+ "examples": null
43851
43845
  },
43852
43846
  {
43853
- "id": "zindex",
43854
- "label": "Zindex",
43855
- "description": "ZIndexes are managed automatically to make sure layering of overlay components work seamlessly when combining multiple components. Still there may be cases where you'd like to configure the configure default values such as a custom layout where header section is fixed. In a case like this, dropdown needs to be displayed below the application header but a modal dialog should be displayed above. ExhaustiveUI configuration offers the zIndex property to customize the default values for components categories. Default values are described below and can be customized when setting up ExhaustiveUI.",
43856
- "examples": {
43857
- "typescript": "import { ExhaustiveConfig } from '@exhaustive-ui/core/api';\n\n@Component({\n selector: 'app-root',\n templateUrl: './app.component.html'\n})\nexport class AppComponent implements OnInit {\n\n constructor(private exhaustiveConfig: ExhaustiveConfig) {}\n\n ngOnInit() {\n this.exhaustiveConfig.zIndex = {\n modal: 1100, // dialog, sidebar\n overlay: 1000, // dropdown, overlaypanel\n menu: 1000, // overlay menus\n tooltip: 1100 // tooltip\n };\n }\n}"
43858
- }
43847
+ "id": "api",
43848
+ "label": "API",
43849
+ "description": "### Locale Options",
43850
+ "examples": null
43859
43851
  }
43860
43852
  ]
43861
43853
  },
@@ -43868,61 +43860,69 @@
43868
43860
  {
43869
43861
  "id": "architecture",
43870
43862
  "label": "Architecture",
43871
- "description": "ExhaustiveUI is a design agnostic library so unlike some other UI libraries it does not enforce a certain styling such as material design. Styling is decoupled from the components using the themes instead. A theme consists of two parts; base and preset . The base is the style rules with CSS variables as placeholders whereas the preset is a set of design tokens to feed a base by mapping the tokens to CSS variables. A base may be configured with different presets, currently Aura, Material, Lara and Nora are the available built-in options. The core of the styled mode architecture is based on a concept named design token , a preset defines the token configuration in 3 tiers; primitive , semantic and component . Primitive Tokens Primitive tokens have no context, a color palette is a good example for a primitive token such as blue-50 to blue-900 . A token named blue-500 may be used as the primary color, the background of a message however on its own, the name of the token does not indicate context. Usually they are utilized by the semantic tokens. Semantic Tokens Semantic tokens define content and their names indicate where they are utilized, a well known example of a semantic token is the primary.color . Semantic tokens map to primitive tokens or other semantic tokens. The colorScheme token group is a special variable to define tokens based on the color scheme active in the application, this allows defining different tokens based on the color scheme like dark mode. Component Tokens Component tokens are isolated tokens per component such as inputtext.background or button.color that map to the semantic tokens. As an example, button.background component token maps to the primary.color semantic token which maps to the green.500 primitive token. Best Practices Use primitive tokens when defining the core color palette and semantic tokens to specify the common design elements such as focus ring, primary colors and surfaces. Components tokens should only be used when customizing a specific component. By defining your own design tokens as a custom preset, you'll be able to define your own style without touching CSS. Overriding the ExhaustiveUI components using style classes is not a best practice and should be the last resort, design tokens are the suggested approach.",
43863
+ "description": "ExhaustiveUI is a design agnostic library so unlike some other UI libraries it does not enforce a certain styling such as material design. Styling is decoupled from the components using the themes instead. A theme consists of two\nparts;\n`base` and `preset`. The base is the style rules with CSS variables as placeholders whereas the preset is a set of design tokens to feed a base by mapping the tokens to CSS variables. A base may be configured with different\npresets, currently Aura, Material, Lara and Nora are the available built-in options.\n\nThe core of the styled mode architecture is based on a concept named `design token`, a preset defines the token configuration in 3 tiers; `primitive`, `semantic` and `component`.\n\n### Primitive Tokens\n\nPrimitive tokens have no context, a color palette is a good example for a primitive token such as `blue-50` to `blue-900`. A token named `blue-500` may be used as the primary color, the background of a message however\non its own, the name of the token does not indicate context. Usually they are utilized by the semantic tokens.\n\n### Semantic Tokens\n\nSemantic tokens define content and their names indicate where they are utilized, a well known example of a semantic token is the `primary.color`. Semantic tokens map to primitive tokens or other semantic tokens. The\n`colorScheme` token group is a special variable to define tokens based on the color scheme active in the application, this allows defining different tokens based on the color scheme like dark mode.\n\n### Component Tokens\n\nComponent tokens are isolated tokens per component such as `inputtext.background` or `button.color` that map to the semantic tokens. As an example, `button.background` component token maps to the\n`primary.color` semantic token which maps to the `green.500` primitive token.\n\n### Best Practices\n\nUse primitive tokens when defining the core color palette and semantic tokens to specify the common design elements such as focus ring, primary colors and surfaces. Components tokens should only be used when customizing a specific\ncomponent. By defining your own design tokens as a custom preset, you'll be able to define your own style without touching CSS. Overriding the ExhaustiveUI components using style classes is not a best practice and should be the last\nresort, design tokens are the suggested approach.",
43872
43864
  "examples": null
43873
43865
  },
43874
43866
  {
43875
- "id": "bootstrap",
43876
- "label": "Bootstrap",
43877
- "description": "Bootstrap has a reboot utility to reset the CSS of the standard elements. If you are including this utility, you may give it a layer while importing it.",
43878
- "examples": null
43867
+ "id": "theme",
43868
+ "label": "Theme",
43869
+ "description": "The `theme` property is used to customize the initial theme.",
43870
+ "examples": {
43871
+ "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n theme: {\n preset: Aura\n }\n })\n ]\n};"
43872
+ }
43879
43873
  },
43880
43874
  {
43881
- "id": "colors",
43882
- "label": "Colors",
43883
- "description": "Color palette of a preset is defined by the primitive design token group. You can access colors using CSS variables or the $dt utility. @for (color of colors; track color) { {{ color }} @for (shade of shades; track shade) { {{ shade }} } }",
43875
+ "id": "options",
43876
+ "label": "Options",
43877
+ "description": "The `options` property defines the how the CSS would be generated from the design tokens of the preset.\n\nprefix\n\nThe prefix of the CSS variables, defaults to `p`. For instance, the `primary.color` design token would be `var(--p-primary-color)`.\n\ndarkModeSelector\n\nThe CSS rule to encapsulate the CSS variables of the dark mode, the default is the `system` to generate `{{ '@' }}media (prefers-color-scheme: dark)`. If you need to make the dark mode toggleable based on the user selection\ndefine a class selector such as `.app-dark` and toggle this class at the document root. See the dark mode toggle section for an example.\n\ncssLayer\n\nDefines whether the styles should be defined inside a\n[CSS layer](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer)\nby default or not. A CSS layer would be handy to declare a custom cascade layer for easier customization if necessary. The default is `false`.",
43884
43878
  "examples": null
43885
43879
  },
43886
43880
  {
43887
- "id": "colorscheme",
43888
- "label": "Colorscheme",
43889
- "description": "A token can be defined per color scheme using light and dark properties of the colorScheme property. Each token can have specific values based on the current color scheme. Common Pitfall When customizing an existing preset, your token overrides may be ignored if you don't properly account for color scheme variations. If the original preset defines a token using the colorScheme property, but your customization only provides a direct value, your override will be ignored because the colorScheme property takes precedence over direct values and the system will continue using the preset's scheme-specific values. When customizing tokens that are not defined with colorScheme in the original preset, your customizations will be applied successfully regardless of how you structure them; whether direct or under colorScheme. Best Practices Check how tokens are defined in the preset before customizing from the source . Always maintain the same structure (direct value or colorScheme) as the original preset. Consider both light and dark mode values when overriding scheme-dependent tokens. This approach ensures your customizations will be applied correctly regardless of the user's selected color scheme.",
43881
+ "id": "presets",
43882
+ "label": "Presets",
43883
+ "description": "Aura, Material, Lara and Nora are the available built-in options, created to demonstrate the power of the design-agnostic theming. Aura is PrimeTek's own vision, Material follows Google Material Design v2, Lara is based on Bootstrap\nand Nora is inspired by enterprise applications. Visit the [source code](https://github.com/e-xiste/exhaustive-ui/tree/main/packages/themes/src/presets) to learn more about the\nstructure of presets. You may use them out of the box with modifications or utilize them as reference in case you need to build your own presets from scratch.",
43890
43884
  "examples": null
43891
43885
  },
43892
43886
  {
43893
- "id": "component",
43894
- "label": "Component",
43895
- "description": "The design tokens of a specific component is defined at components layer. Overriding components tokens is not the recommended approach if you are building your own style, building your own preset should be preferred instead. This configuration is global and applies to all card components, in case you need to customize a particular component on a page locally, view the Scoped CSS section for an example.",
43887
+ "id": "colors",
43888
+ "label": "Colors",
43889
+ "description": "Color palette of a preset is defined by the `primitive` design token group. You can access colors using CSS variables or the `$dt` utility.\n\n@for (color of colors; track color) {\n- {{ color }} @for (shade of shades; track shade) { {{ shade }} }\n}",
43896
43890
  "examples": null
43897
43891
  },
43898
43892
  {
43899
43893
  "id": "darkmode",
43900
- "label": "Darkmode",
43901
- "description": "ExhaustiveUI uses the system as the default darkModeSelector in theme configuration. If you have a dark mode switch in your application, set the darkModeSelector to the selector you utilize such as .my-app-dark so that ExhaustiveUI can fit in seamlessly with your color scheme. Following is a very basic example implementation of a dark mode switch, you may extend it further by involving prefers-color-scheme to retrieve it from the system initially and use localStorage to make it stateful. See this article for more information. In case you prefer to use dark mode all the time, apply the darkModeSelector initially and never change it. It is also possible to disable dark mode completely using false or none as the value of the selector.",
43894
+ "label": "Dark Mode",
43895
+ "description": "ExhaustiveUI uses the `system` as the default `darkModeSelector` in theme configuration. If you have a dark mode switch in your application, set the `darkModeSelector` to the selector you utilize such as\n`.my-app-dark` so that ExhaustiveUI can fit in seamlessly with your color scheme.\n\n```typescript\nprovideExhaustive({\n theme: {\n preset: Aura,\n options: {\n darkModeSelector: '.my-app-dark'\n }\n }\n})\n```\n\nFollowing is a very basic example implementation of a dark mode switch, you may extend it further by involving\n`prefers-color-scheme` to retrieve it from the system initially and use `localStorage` to make it stateful. See this\n[article](https://dev.to/abbeyperini/dark-mode-toggle-and-prefers-color-scheme-4f3m)\nfor more information.\n\nIn case you prefer to use dark mode all the time, apply the `darkModeSelector` initially and never change it.\n\nIt is also possible to disable dark mode completely using `false` or `none` as the value of the selector.\n\n```typescript\nprovideExhaustive({\n theme: {\n preset: Aura,\n options: {\n darkModeSelector: false || 'none'\n }\n }\n})\n```",
43902
43896
  "examples": null
43903
43897
  },
43904
43898
  {
43905
43899
  "id": "definepreset",
43906
- "label": "Definepreset",
43907
- "description": "The definePreset utility is used to customize an existing preset during the ExhaustiveUI setup. The first parameter is the preset to customize and the second is the design tokens to override.",
43900
+ "label": "definePreset",
43901
+ "description": "The `definePreset` utility is used to customize an existing preset during the ExhaustiveUI setup. The first parameter is the preset to customize and the second is the design tokens to override.",
43908
43902
  "examples": null
43909
43903
  },
43910
43904
  {
43911
- "id": "dt",
43912
- "label": "Dt",
43913
- "description": "The $dt function returns the information about a token like the full path and value. This would be useful if you need to access tokens programmatically.",
43905
+ "id": "colorscheme",
43906
+ "label": "Color Scheme",
43907
+ "description": "A token can be defined per color scheme using `light` and `dark` properties of the `colorScheme` property. Each token can have specific values based on the current color scheme.\n\nCommon Pitfall\n\nWhen customizing an existing preset, your token overrides may be ignored if you don't properly account for color scheme variations. If the original preset defines a token using the `colorScheme` property, but your customization\nonly provides a direct value, your override will be ignored because the `colorScheme` property takes precedence over direct values and the system will continue using the preset's scheme-specific values. When customizing tokens\nthat are not defined with `colorScheme` in the original preset, your customizations will be applied successfully regardless of how you structure them; whether direct or under colorScheme.\n\nBest Practices\n\n- Check how tokens are defined in the preset before customizing from the [source](https://github.com/e-xiste/exhaustive-ui/blob/main/packages/themes/src/presets).\n- Always maintain the same structure (direct value or colorScheme) as the original preset.\n- Consider both light and dark mode values when overriding scheme-dependent tokens.\n\nThis approach ensures your customizations will be applied correctly regardless of the user's selected color scheme.",
43914
43908
  "examples": null
43915
43909
  },
43916
43910
  {
43917
- "id": "extend",
43918
- "label": "Extend",
43919
- "description": "The theming system can be extended by adding custom design tokens and additional styles. This feature provides a high degree of customization, allowing you to adjust styles according to your needs, as you are not limited to the default tokens. The example preset configuration adds a new accent button with custom button.accent.color and button.accent.inverse.color tokens. It is also possible to add tokens globally to share them within the components.",
43911
+ "id": "primary",
43912
+ "label": "Primary",
43913
+ "description": "The `primary` defines the main color palette, default value maps to the `emerald` primitive token. Let's setup to use `indigo` instead.",
43920
43914
  "examples": null
43921
43915
  },
43922
43916
  {
43923
- "id": "focusring",
43924
- "label": "Focusring",
43925
- "description": "Focus ring defines the outline width, style, color and offset. Let's use a thicker ring with the primary color for the outline.",
43917
+ "id": "surface",
43918
+ "label": "Surface",
43919
+ "description": "The color scheme palette that varies between light and dark modes is specified with the surface tokens. Example below uses\n`zinc` for light mode and `slategray` for dark mode. With this setting, light mode, would have a grayscale tone and dark mode would include bluish tone.",
43920
+ "examples": null
43921
+ },
43922
+ {
43923
+ "id": "noir",
43924
+ "label": "Noir",
43925
+ "description": "The `noir` mode is the nickname of a variant that uses surface tones as the primary and requires and additional `colorScheme` configuration to implement. A sample preset configuration with black and white variants as the\nprimary color;",
43926
43926
  "examples": null
43927
43927
  },
43928
43928
  {
@@ -43934,105 +43934,97 @@
43934
43934
  {
43935
43935
  "id": "forms",
43936
43936
  "label": "Forms",
43937
- "description": "The design tokens of the form input components are derived from the form.field token group. This customization example changes border color to primary on hover. Any component that depends on this semantic token such as dropdown.hover.border.color and textarea.hover.border.color would receive the change.",
43937
+ "description": "The design tokens of the form input components are derived from the `form.field` token group. This customization example changes border color to primary on hover. Any component that depends on this semantic token such as\n`dropdown.hover.border.color` and `textarea.hover.border.color` would receive the change.",
43938
43938
  "examples": null
43939
43939
  },
43940
43940
  {
43941
- "id": "libraries",
43942
- "label": "Libraries",
43943
- "description": "Example layer configuration for the popular CSS libraries.",
43941
+ "id": "focusring",
43942
+ "label": "Focus Ring",
43943
+ "description": "Focus ring defines the outline width, style, color and offset. Let's use a thicker ring with the primary color for the outline.",
43944
43944
  "examples": null
43945
43945
  },
43946
43946
  {
43947
- "id": "noir",
43948
- "label": "Noir",
43949
- "description": "The noir mode is the nickname of a variant that uses surface tones as the primary and requires and additional colorScheme configuration to implement. A sample preset configuration with black and white variants as the primary color;",
43947
+ "id": "component",
43948
+ "label": "Component",
43949
+ "description": "The design tokens of a specific component is defined at `components` layer. Overriding components tokens is not the recommended approach if you are building your own style, building your own preset should be preferred instead.\nThis configuration is global and applies to all card components, in case you need to customize a particular component on a page locally, view the Scoped CSS section for an example.",
43950
43950
  "examples": null
43951
43951
  },
43952
43952
  {
43953
- "id": "options",
43954
- "label": "Options",
43955
- "description": "The options property defines the how the CSS would be generated from the design tokens of the preset. prefix The prefix of the CSS variables, defaults to p . For instance, the primary.color design token would be var(--p-primary-color) . darkModeSelector The CSS rule to encapsulate the CSS variables of the dark mode, the default is the system to generate {{ '@' }}media (prefers-color-scheme: dark) . If you need to make the dark mode toggleable based on the user selection define a class selector such as .app-dark and toggle this class at the document root. See the dark mode toggle section for an example. cssLayer Defines whether the styles should be defined inside a CSS layer by default or not. A CSS layer would be handy to declare a custom cascade layer for easier customization if necessary. The default is false .",
43953
+ "id": "extend",
43954
+ "label": "Extend",
43955
+ "description": "The theming system can be extended by adding custom design tokens and additional styles. This feature provides a high degree of customization, allowing you to adjust styles according to your needs, as you are not limited to the\ndefault tokens.\n\nThe example preset configuration adds a new `accent` button with custom `button.accent.color` and `button.accent.inverse.color` tokens. It is also possible to add tokens globally to share them within the components.",
43956
43956
  "examples": null
43957
43957
  },
43958
43958
  {
43959
- "id": "palette",
43960
- "label": "Palette",
43961
- "description": "Returns shades and tints of a given color from 50 to 950 as an array.",
43959
+ "id": "scopedtokens",
43960
+ "label": "Scoped Tokens",
43961
+ "description": "Design tokens can be scoped to a certain component using the `dt` property. In this example, first switch uses the global tokens whereas second one overrides the global with its own tokens.\n\nThis approach is recommended over the `::ng-deep` as it offers a cleaner API while avoiding the hassle of CSS rule overrides.",
43962
43962
  "examples": null
43963
43963
  },
43964
43964
  {
43965
- "id": "presets",
43966
- "label": "Presets",
43967
- "description": "Aura, Material, Lara and Nora are the available built-in options, created to demonstrate the power of the design-agnostic theming. Aura is PrimeTek's own vision, Material follows Google Material Design v2, Lara is based on Bootstrap and Nora is inspired by enterprise applications. Visit the source code to learn more about the structure of presets. You may use them out of the box with modifications or utilize them as reference in case you need to build your own presets from scratch.",
43965
+ "id": "usepreset",
43966
+ "label": "usePreset",
43967
+ "description": "Replaces the current presets entirely, common use case is changing the preset dynamically at runtime.",
43968
43968
  "examples": null
43969
43969
  },
43970
43970
  {
43971
- "id": "primary",
43972
- "label": "Primary",
43973
- "description": "The primary defines the main color palette, default value maps to the emerald primitive token. Let's setup to use indigo instead.",
43971
+ "id": "updatepreset",
43972
+ "label": "updatePreset",
43973
+ "description": "Merges the provided tokens to the current preset, an example would be changing the primary color palette dynamically.",
43974
43974
  "examples": null
43975
43975
  },
43976
43976
  {
43977
- "id": "reset",
43978
- "label": "Reset",
43979
- "description": "In case ExhaustiveUI components have visual issues in your application, a Reset CSS may be the culprit. CSS layers would be an efficient solution that involves enabling the ExhaustiveUI layer, wrapping the Reset CSS in another layer and defining the layer order. This way, your Reset CSS does not get in the way of ExhaustiveUI components.",
43977
+ "id": "updateprimarypalette",
43978
+ "label": "updatePrimaryPalette",
43979
+ "description": "Updates the primary colors, this is a shorthand to do the same update using `updatePreset`.",
43980
43980
  "examples": null
43981
43981
  },
43982
43982
  {
43983
- "id": "scale",
43984
- "label": "Scale",
43985
- "description": "ExhaustiveUI UI component use rem units, 1rem equals to the font size of the html element which is 16px by default. Use the root font-size to adjust the size of the components globally. This website uses 14px as the base so it may differ from your application if your base font size is different.",
43983
+ "id": "updatesurfacepalette",
43984
+ "label": "updateSurfacePalette",
43985
+ "description": "Updates the surface colors, this is a shorthand to do the same update using `updatePreset`.",
43986
43986
  "examples": null
43987
43987
  },
43988
43988
  {
43989
- "id": "scopedtokens",
43990
- "label": "Scopedtokens",
43991
- "description": "Design tokens can be scoped to a certain component using the dt property. In this example, first switch uses the global tokens whereas second one overrides the global with its own tokens. This approach is recommended over the ::ng-deep as it offers a cleaner API while avoiding the hassle of CSS rule overrides.",
43989
+ "id": "dt",
43990
+ "label": "$dt",
43991
+ "description": "The `$dt` function returns the information about a token like the full path and value. This would be useful if you need to access tokens programmatically.",
43992
43992
  "examples": null
43993
43993
  },
43994
43994
  {
43995
- "id": "specificity",
43996
- "label": "Specificity",
43997
- "description": "The @layer is a standard CSS feature to define cascade layers for a customizable order of precedence. If you need to become more familiar with layers, visit the documentation at MDN to begin with. The cssLayer is disabled by default, when it is enabled at theme configuration, ExhaustiveUI wraps the built-in style classes under the exhaustive cascade layer to make the library styles easy to override. CSS in your app without a layer has the highest CSS specificity, so you'll be able to override styles regardless of the location or how strong a class is written.",
43995
+ "id": "Palette",
43996
+ "label": "palette",
43997
+ "description": "Returns shades and tints of a given color from 50 to 950 as an array.",
43998
43998
  "examples": null
43999
43999
  },
44000
44000
  {
44001
- "id": "surface",
44002
- "label": "Surface",
44003
- "description": "The color scheme palette that varies between light and dark modes is specified with the surface tokens. Example below uses zinc for light mode and slategray for dark mode. With this setting, light mode, would have a grayscale tone and dark mode would include bluish tone.",
44001
+ "id": "specificity",
44002
+ "label": "Specificity",
44003
+ "description": "The `@layer` is a standard CSS feature to define cascade layers for a customizable order of precedence. If you need to become more familiar with layers, visit the documentation at\n[MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) to begin with.\n\nThe `cssLayer` is disabled by default, when it is enabled at theme configuration, ExhaustiveUI wraps the built-in style classes under the `exhaustive` cascade layer to make the library styles easy to override. CSS in your\napp without a layer has the highest CSS specificity, so you'll be able to override styles regardless of the location or how strong a class is written.",
44004
44004
  "examples": null
44005
44005
  },
44006
44006
  {
44007
- "id": "theme",
44008
- "label": "Theme",
44009
- "description": "The theme property is used to customize the initial theme.",
44010
- "examples": {
44011
- "typescript": "import { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n theme: {\n preset: Aura\n }\n })\n ]\n};"
44012
- }
44013
- },
44014
- {
44015
- "id": "updatepreset",
44016
- "label": "Updatepreset",
44017
- "description": "Merges the provided tokens to the current preset, an example would be changing the primary color palette dynamically.",
44007
+ "id": "reset",
44008
+ "label": "Reset",
44009
+ "description": "In case ExhaustiveUI components have visual issues in your application, a Reset CSS may be the culprit. CSS layers would be an efficient solution that involves enabling the ExhaustiveUI layer, wrapping the Reset CSS in another layer\nand defining the layer order. This way, your Reset CSS does not get in the way of ExhaustiveUI components.",
44018
44010
  "examples": null
44019
44011
  },
44020
44012
  {
44021
- "id": "updateprimarypalette",
44022
- "label": "Updateprimarypalette",
44023
- "description": "Updates the primary colors, this is a shorthand to do the same update using updatePreset .",
44013
+ "id": "scale",
44014
+ "label": "Scale",
44015
+ "description": "ExhaustiveUI UI component use `rem` units, 1rem equals to the font size of the `html` element which is `16px` by default. Use the root font-size to adjust the size of the components globally. This website uses\n`14px` as the base so it may differ from your application if your base font size is different.",
44024
44016
  "examples": null
44025
44017
  },
44026
44018
  {
44027
- "id": "updatesurfacepalette",
44028
- "label": "Updatesurfacepalette",
44029
- "description": "Updates the surface colors, this is a shorthand to do the same update using updatePreset .",
44019
+ "id": "bootstrap",
44020
+ "label": "Bootstrap",
44021
+ "description": "Bootstrap has a `reboot` utility to reset the CSS of the standard elements. If you are including this utility, you may give it a layer while importing it.",
44030
44022
  "examples": null
44031
44023
  },
44032
44024
  {
44033
- "id": "usepreset",
44034
- "label": "Usepreset",
44035
- "description": "Replaces the current presets entirely, common use case is changing the preset dynamically at runtime.",
44025
+ "id": "libraries",
44026
+ "label": "Libraries",
44027
+ "description": "Example layer configuration for the popular CSS libraries.",
44036
44028
  "examples": null
44037
44029
  }
44038
44030
  ]
@@ -44046,27 +44038,25 @@
44046
44038
  {
44047
44039
  "id": "architecture",
44048
44040
  "label": "Architecture",
44049
- "description": "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.",
44041
+ "description": "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\nincluded. Here is an example of an Unstyled Select, the core functionality and accessibility is provided whereas styling is not included.",
44042
+ "examples": null
44043
+ },
44044
+ {
44045
+ "id": "setup",
44046
+ "label": "Setup",
44047
+ "description": "Unstyled mode is enabled for the whole suite by enabling `unstyled` option during ExhaustiveUI installation.\n\n```typescript\nimport { ApplicationConfig } from '@angular/core';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n unstyled: true\n })\n ]\n};\n```\n\nAlternatively even in the default styled mode, a particular component can still be used as unstyled by adding the `unstyled` prop of the component.\n\n```html\n<div class=\"card flex justify-center items-center gap-2\">\n <p-button label=\"Styled\" icon=\"pi pi-check\" />\n <p-button label=\"Unstyled\" icon=\"pi pi-check\" [unstyled]=\"true\" />\n</div>\n```",
44050
44048
  "examples": null
44051
44049
  },
44052
44050
  {
44053
44051
  "id": "example",
44054
44052
  "label": "Example",
44055
- "description": "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.",
44053
+ "description": "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\nvariants such as `p-outlined:`, `p-vertical` for the ExhaustiveUI components.\n\nThe example below demonstrates how to style a button component with Tailwind CSS using PassThrough attributes. Before you begin, refer to the\npass through section in the button documentation to familiarize yourself with the component's internal structure and PassThrough attributes. In this\nexample, we'll target the `root`, `label` and `icon` elements to apply custom styles.\n\n```html\n<p-button\n label=\"Search\"\n icon=\"pi pi-search\"\n [unstyled]=\"true\"\n [pt]=\"{\n root: 'bg-teal-500 hover:bg-teal-700 active:bg-teal-900 cursor-pointer py-2 px-4 rounded-full border-0 flex gap-2',\n label: 'text-white font-bold text-lg',\n icon: 'text-white text-xl!'\n }\"\n/>\n```",
44056
44054
  "examples": null
44057
44055
  },
44058
44056
  {
44059
44057
  "id": "global",
44060
44058
  "label": "Global",
44061
- "description": "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.",
44062
- "examples": {
44063
- "typescript": "import { ApplicationConfig } from '@angular/core';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n unstyled: true,\n pt: {\n button: {\n root: 'bg-teal-500 hover:bg-teal-700 active:bg-teal-900 cursor-pointer py-2 px-4 rounded-full border-0 flex gap-2',\n label: 'text-white font-bold text-lg',\n icon: 'text-white text-xl!'\n }\n }\n })\n ]\n};"
44064
- }
44065
- },
44066
- {
44067
- "id": "setup",
44068
- "label": "Setup",
44069
- "description": "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.",
44059
+ "description": "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\nwith its own `pt` property.\n\n```typescript\nimport { ApplicationConfig } from '@angular/core';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n unstyled: true,\n pt: {\n button: {\n root: 'bg-teal-500 hover:bg-teal-700 active:bg-teal-900 cursor-pointer py-2 px-4 rounded-full border-0 flex gap-2',\n label: 'text-white font-bold text-lg',\n icon: 'text-white text-xl!'\n }\n }\n })\n ]\n};\n```",
44070
44060
  "examples": null
44071
44061
  }
44072
44062
  ]
@@ -44077,26 +44067,6 @@
44077
44067
  "title": "Icons",
44078
44068
  "description": "OpenNG Icons is the default icon library of ExhaustiveUI with over 250 open source icons.",
44079
44069
  "sections": [
44080
- {
44081
- "id": "basic",
44082
- "label": "Basic",
44083
- "description": "OpenNG Icons use the pi pi-{icon} syntax such as pi pi-check . A standalone icon can be displayed using an element such as i or span",
44084
- "examples": null
44085
- },
44086
- {
44087
- "id": "color",
44088
- "label": "Color",
44089
- "description": "Icon color is defined with the color property which is inherited from parent by default.",
44090
- "examples": null
44091
- },
44092
- {
44093
- "id": "constants",
44094
- "label": "Constants",
44095
- "description": "Constants API is available to reference icons easily when used programmatically.",
44096
- "examples": {
44097
- "typescript": "import { Component } from '@angular/core';\nimport { OpenngIcons, MenuItem } from '@exhaustive-ui/core/api';\n\n@Component({\n selector: 'openng-icons-constants-demo',\n templateUrl: './openng-icons-constants-demo.html'\n})\nexport class OpenngIconsConstantsDemo {\n items: MenuItem[];\n\n ngOnInit() {\n this.items = [\n {\n label: 'New',\n icon: OpenngIcons.PLUS,\n },\n {\n label: 'Delete',\n icon: OpenngIcons.TRASH\n }\n ];\n }\n}"
44098
- }
44099
- },
44100
44070
  {
44101
44071
  "id": "download",
44102
44072
  "label": "Download",
@@ -44108,15 +44078,15 @@
44108
44078
  {
44109
44079
  "id": "import",
44110
44080
  "label": "Import",
44111
- "description": "CSS file of the icon library needs to be imported in styles.scss of your application.",
44081
+ "description": "CSS file of the icon library needs to be imported in `styles.scss` of your application.",
44112
44082
  "examples": {
44113
44083
  "scss": "@import \"@openng/icons/openng-icons.css\";"
44114
44084
  }
44115
44085
  },
44116
44086
  {
44117
- "id": "list",
44118
- "label": "List",
44119
- "description": "Here is the full list of icons. More icons will be added periodically and you may also request new icons at the issue tracker.",
44087
+ "id": "basic",
44088
+ "label": "Basic",
44089
+ "description": "OpenNG Icons use the `pi pi-{icon}` syntax such as `pi pi-check`. A standalone icon can be displayed using an element such as `i` or `span`",
44120
44090
  "examples": null
44121
44091
  },
44122
44092
  {
@@ -44125,10 +44095,30 @@
44125
44095
  "description": "Size of an icon is controlled with the font-size property of the element.",
44126
44096
  "examples": null
44127
44097
  },
44098
+ {
44099
+ "id": "color",
44100
+ "label": "Color",
44101
+ "description": "Icon color is defined with the `color` property which is inherited from parent by default.",
44102
+ "examples": null
44103
+ },
44128
44104
  {
44129
44105
  "id": "spin",
44130
44106
  "label": "Spin",
44131
- "description": "Special pi-spin class applies infinite rotation to an icon.",
44107
+ "description": "Special `pi-spin` class applies infinite rotation to an icon.",
44108
+ "examples": null
44109
+ },
44110
+ {
44111
+ "id": "constants",
44112
+ "label": "Constants",
44113
+ "description": "Constants API is available to reference icons easily when used programmatically.",
44114
+ "examples": {
44115
+ "typescript": "import { Component } from '@angular/core';\nimport { OpenngIcons, MenuItem } from '@exhaustive-ui/core/api';\n\n@Component({\n selector: 'openng-icons-constants-demo',\n templateUrl: './openng-icons-constants-demo.html'\n})\nexport class OpenngIconsConstantsDemo {\n items: MenuItem[];\n\n ngOnInit() {\n this.items = [\n {\n label: 'New',\n icon: OpenngIcons.PLUS,\n },\n {\n label: 'Delete',\n icon: OpenngIcons.TRASH\n }\n ];\n }\n}"
44116
+ }
44117
+ },
44118
+ {
44119
+ "id": "list",
44120
+ "label": "List",
44121
+ "description": "Here is the full list of icons. More icons will be added periodically and you may also\n[request new icons](https://github.com/openng-org/icons/issues) at the issue tracker.",
44132
44122
  "examples": null
44133
44123
  }
44134
44124
  ]
@@ -44140,27 +44130,27 @@
44140
44130
  "description": "Use custom icons with ExhaustiveUI components.",
44141
44131
  "sections": [
44142
44132
  {
44143
- "id": "fontawesome",
44144
- "label": "Fontawesome",
44145
- "description": "Font Awesome is a popular icon library with a wide range of icons.",
44133
+ "id": "material",
44134
+ "label": "Material",
44135
+ "description": "[Material icons](https://fonts.google.com/icons) is the official icon library based on Google Material Design.",
44146
44136
  "examples": null
44147
44137
  },
44148
44138
  {
44149
- "id": "image",
44150
- "label": "Image",
44151
- "description": "Any type of image can be used as an icon.",
44139
+ "id": "fontawesome",
44140
+ "label": "Font Awesome",
44141
+ "description": "[Font Awesome](https://fontawesome.com/) is a popular icon library with a wide range of icons.",
44152
44142
  "examples": null
44153
44143
  },
44154
44144
  {
44155
- "id": "material",
44156
- "label": "Material",
44157
- "description": "Material icons is the official icon library based on Google Material Design.",
44145
+ "id": "svg",
44146
+ "label": "SVG",
44147
+ "description": "Inline SVGs are embedded inside the dom.",
44158
44148
  "examples": null
44159
44149
  },
44160
44150
  {
44161
- "id": "svg",
44162
- "label": "Svg",
44163
- "description": "Inline SVGs are embedded inside the dom.",
44151
+ "id": "image",
44152
+ "label": "Image",
44153
+ "description": "Any type of image can be used as an icon.",
44164
44154
  "examples": null
44165
44155
  }
44166
44156
  ]
@@ -44174,43 +44164,43 @@
44174
44164
  {
44175
44165
  "id": "basic",
44176
44166
  "label": "Basic",
44177
- "description": "Each component has a special pt property to define an object with keys corresponding to the available DOM elements. Each value can either be a string, an object or a function that returns a string or an object to define the arbitrary properties to apply to the element such as styling, aria, data-* or custom attributes. If the value is a string or a function that returns a string, it is considered as a class definition and added to the class attribute of the element. Every component documentation has a dedicated section to document the available section names exposed via PT.",
44167
+ "description": "Each component has a special `pt` property to define an object with keys corresponding to the available DOM elements. Each value can either be a string, an object or a function that returns a string or an object to define the\narbitrary properties to apply to the element such as styling, aria, data-* or custom attributes. If the value is a string or a function that returns a string, it is considered as a class definition and added to the class attribute of\nthe element. Every component documentation has a dedicated section to document the available section names exposed via PT.",
44178
44168
  "examples": null
44179
44169
  },
44180
44170
  {
44181
44171
  "id": "global",
44182
44172
  "label": "Global",
44183
- "description": "PassThrough object can also be defined at a global level to apply all components in an application using the provideExhaustive provider. For example, with the configuration here all panel headers have the bg-primary style class and all autocomplete components have a fixed width. These settings can be overridden by a particular component as components pt property has higher precedence over global pt by default.",
44173
+ "description": "PassThrough object can also be defined at a global level to apply all components in an application using the `provideExhaustive` provider. For example, with the configuration here all panel headers have the\n`bg-primary` style class and all autocomplete components have a fixed width. These settings can be overridden by a particular component as components `pt` property has higher precedence over global `pt` by default.",
44184
44174
  "examples": null
44185
44175
  },
44186
44176
  {
44187
44177
  "id": "instance",
44188
44178
  "label": "Instance",
44189
- "description": "In cases where you need to access the UI Component instance, define a component passthrough type that exposes the component instance or a function that receives a PassThroughContext as parameter.",
44179
+ "description": "In cases where you need to access the UI Component instance, define a component passthrough type that exposes the component instance or a function that receives a `PassThroughContext` as parameter.",
44190
44180
  "examples": null
44191
44181
  },
44192
44182
  {
44193
44183
  "id": "introduction",
44194
44184
  "label": "Introduction",
44195
- "description": "In traditional 3rd party UI libraries, users are limited to the API provided by component author. This API commonly consists of inputs, outputs, and content projection. Whenever a requirement emerges for a new customization option in the API, the component author needs to develop and publish it with a new release. The pass through feature is a key element to implement this vision by exposing the component internals in order to apply arbitrary attributes and listeners to the DOM elements. The primary advantage of this approach is that it frees you from being restricted by the main component API. We recommend considering the pass-through feature whenever you need to tailor a component that lacks a built-in feature for your specific requirement. Each component has a special pt property to define an object with keys corresponding to the available DOM elements. A value of a key can either be a string, an object or a function to define the arbitrary properties such as styling, aria, data-* or custom attributes for the element. If the value is a string or a function that returns a string, it serves as a shorthand for a style class definition. Every component documentation has a dedicated segment to document the available section names in the interactive PT Viewer. Panel Example In this example, a Panel is customized with various options through pt . The styling is overriden with Tailwind CSS and header receives custom attributes along with a click event. The attributes passed to the header are not available in the component API, thanks to PassThrough feature, this is no longer an issue as you are not limited to the component api. Note that, you may avoid the ! based overrides in Tailwind classes if you setup CSS Layers with ExhaustiveUI. Visit the Override section at Tailwind integration for examples.",
44185
+ "description": "In traditional 3rd party UI libraries, users are limited to the API provided by component author. This API commonly consists of inputs, outputs, and content projection. Whenever a requirement emerges for a new customization option in\nthe API, the component author needs to develop and publish it with a new release.\n\nThe pass through feature is a key element to implement this vision by exposing the component internals in order to apply arbitrary attributes and listeners to the DOM elements. The primary advantage of this approach is that it frees\nyou from being restricted by the main component API. We recommend considering the pass-through feature whenever you need to tailor a component that lacks a built-in feature for your specific requirement.\n\nEach component has a special `pt` property to define an object with keys corresponding to the available DOM elements. A value of a key can either be a string, an object or a function to define the arbitrary properties such as\nstyling, aria, data-* or custom attributes for the element. If the value is a string or a function that returns a string, it serves as a shorthand for a style class definition. Every component documentation has a dedicated segment to\ndocument the available section names in the interactive PT Viewer.\n\n### Panel Example\n\nIn this example, a Panel is customized with various options through `pt`. The styling is overriden with Tailwind CSS and header receives custom attributes along with a click event. The attributes passed to the header are not\navailable in the component API, thanks to PassThrough feature, this is no longer an issue as you are not limited to the component api. Note that, you may avoid the `!` based overrides in Tailwind classes if you setup CSS Layers\nwith ExhaustiveUI. Visit the [Override](https://exhaustive-ui.com/tailwind) section at Tailwind integration for examples.",
44196
44186
  "examples": null
44197
44187
  },
44198
44188
  {
44199
44189
  "id": "lifecycle",
44200
44190
  "label": "Lifecycle",
44201
- "description": "Lifecycle hooks of components are exposed as pass through using the hooks property so that callback functions can be registered. Available callbacks are onBeforeInit , onInit , onChanges , onDoCheck , onAfterContentInit , onAfterContentChecked , onAfterViewInit , onAfterViewChecked and onDestroy . Refer to the Angular documentation for detailed information about lifecycle hooks.",
44191
+ "description": "Lifecycle hooks of components are exposed as pass through using the `hooks` property so that callback functions can be registered. Available callbacks are `onBeforeInit`, `onInit`, `onChanges`, `onDoCheck`,\n`onAfterContentInit`, `onAfterContentChecked`, `onAfterViewInit`, `onAfterViewChecked` and `onDestroy`. Refer to the Angular documentation for detailed information about lifecycle hooks.",
44202
44192
  "examples": null
44203
44193
  },
44204
44194
  {
44205
44195
  "id": "pcprefix",
44206
44196
  "label": "Pcprefix",
44207
- "description": "A UI component may also use other UI components, in this case section names are prefixed with pc (Prime Component) to denote the ExhaustiveUI component begin used. This distinguishes components from standard DOM elements and indicating the necessity for a nested structure. For example, the badge section is identified as pcBadge because the button component incorporates the badge component internally.",
44197
+ "description": "A UI component may also use other UI components, in this case section names are prefixed with `pc` (Prime Component) to denote the ExhaustiveUI component begin used. This distinguishes components from standard DOM elements and\nindicating the necessity for a nested structure. For example, the `badge` section is identified as `pcBadge` because the button component incorporates the badge component internally.",
44208
44198
  "examples": null
44209
44199
  },
44210
44200
  {
44211
44201
  "id": "ptoptions",
44212
44202
  "label": "Ptoptions",
44213
- "description": "The ⁠ptOptions property determines how a component's local PassThrough configuration merges with the global PT configuration, as demonstrated in the following examples using both global and component-level settings. The mergeSections defines whether the sections from the main configuration gets added and the mergeProps controls whether to override or merge the defined props. Defaults are true for mergeSections and false for mergeProps . Global Configuration mergeSections: true, mergeProps: false (default) mergeSections: true, mergeProps: true mergeSections: false, mergeProps: true mergeSections: false, mergeProps: false",
44203
+ "description": "The `⁠ptOptions` property determines how a component's local PassThrough configuration merges with the global PT configuration, as demonstrated in the following examples using both global and component-level settings.\n\nThe `mergeSections` defines whether the sections from the main configuration gets added and the `mergeProps` controls whether to override or merge the defined props. Defaults are `true` for `mergeSections` and\n`false` for `mergeProps`.\n\n### Global Configuration\n\n```typescript\nimport { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideExhaustive({\n pt: {\n panel: {\n header: {\n 'data-custom': 'acme-panel',\n class: 'bg-primary text-primary-contrast'\n },\n content: 'font-medium'\n }\n }\n })\n ]\n};\n```\n\n### mergeSections: true, mergeProps: false (default)\n\n```typescript\nimport { Component } from '@angular/core';\nimport { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';\n\n@Component({\n selector: 'ptoptions-doc',\n template: \\\n```\n\n### mergeSections: true, mergeProps: true\n\n```typescript\nimport { Component } from '@angular/core';\nimport { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';\n\n@Component({\n selector: 'ptoptions-doc',\n template: \\\n```\n\n### mergeSections: false, mergeProps: true\n\n```typescript\nimport { Component } from '@angular/core';\nimport { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';\n\n@Component({\n selector: 'ptoptions-doc',\n template: \\\n```\n\n### mergeSections: false, mergeProps: false\n\n```typescript\nimport { Component } from '@angular/core';\nimport { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';\n\n@Component({\n selector: 'ptoptions-doc',\n template: \\\n```",
44214
44204
  "examples": null
44215
44205
  }
44216
44206
  ]
@@ -44222,33 +44212,43 @@
44222
44212
  "description": "Integration between ExhaustiveUI and Tailwind CSS.",
44223
44213
  "sections": [
44224
44214
  {
44225
- "id": "animations",
44226
- "label": "Animations",
44227
- "description": "The plugin also adds extended animation utilities that can be used with the styleclass and animateonscroll directives.",
44228
- "examples": {
44229
- "typescript": "import { Component, OnInit } from '@angular/core';\nimport { FormsModule } from '@angular/forms';\nimport { SelectModule } from '@exhaustive-ui/core/select';\n\n@Component({\n template: `\n <div class=\"card\">\n <p-select [(ngModel)]=\"animation\" [options]=\"animations\" placeholder=\"Select One\" class=\"w-full sm:w-44\" />\n <div class=\"py-8 overflow-hidden\">\n <div [ngClass]=\"dynamicAnimationClasses\"></div>\n </div>\n </div>\n <h3>Animations</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-fadein</td>\n <td>fadein 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeout</td>\n <td>fadeout 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-slidedown</td>\n <td>slidedown 0.45s ease-in-out</td>\n </tr>\n <tr>\n <td>animate-slideup</td>\n <td>slideup 0.45s cubic-bezier(0, 1, 0, 1)</td>\n </tr>\n <tr>\n <td>animate-scalein</td>\n <td>scalein 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeinleft</td>\n <td>fadeinleft 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutleft</td>\n <td>fadeoutleft 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeinright</td>\n <td>fadeinright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutright</td>\n <td>fadeoutright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeinup</td>\n <td>fadeinup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutup</td>\n <td>fadeoutup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeindown</td>\n <td>fadeindown 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutup</td>\n <td>fadeoutup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-width</td>\n <td>width 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flip</td>\n <td>flip 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flipup</td>\n <td>flipup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flipleft</td>\n <td>fadein 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flipright</td>\n <td>flipright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoomin</td>\n <td>zoomin 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoomindown</td>\n <td>zoomindown 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoominleft</td>\n <td>zoominleft 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoominright</td>\n <td>zoominright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoominup</td>\n <td>zoominup 0.15s linear</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Animation Duration</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-duration-0</td>\n <td>animation-duration: 0s</td>\n </tr>\n <tr>\n <td>animate-duration-75</td>\n <td>animation-duration: 75ms</td>\n </tr>\n <tr>\n <td>animate-duration-100</td>\n <td>animation-duration: 100ms</td>\n </tr>\n <tr>\n <td>animate-duration-200</td>\n <td>animation-duration: 200ms</td>\n </tr>\n <tr>\n <td>animate-duration-300</td>\n <td>animation-duration: 300ms</td>\n </tr>\n <tr>\n <td>animate-duration-400</td>\n <td>animation-duration: 400ms</td>\n </tr>\n <tr>\n <td>animate-duration-500</td>\n <td>animation-duration: 500ms</td>\n </tr>\n <tr>\n <td>animate-duration-700</td>\n <td>animation-duration: 700ms</td>\n </tr>\n <tr>\n <td>animate-duration-1000</td>\n <td>animation-duration: 1000ms</td>\n </tr>\n <tr>\n <td>animate-duration-2000</td>\n <td>animation-duration: 2000ms</td>\n </tr>\n <tr>\n <td>animate-duration-3000</td>\n <td>animation-duration: 300ms</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Animation Delay</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-delay-none</td>\n <td>animation-duration: 0s</td>\n </tr>\n <tr>\n <td>animate-delay-75</td>\n <td>animation-delay: 75ms</td>\n </tr>\n <tr>\n <td>animate-delay-100</td>\n <td>animation-delay: 100ms</td>\n </tr>\n <tr>\n <td>animate-delay-150</td>\n <td>animation-delay: 150ms</td>\n </tr>\n <tr>\n <td>animate-delay-200</td>\n <td>animation-delay: 200ms</td>\n </tr>\n <tr>\n <td>animate-delay-300</td>\n <td>animation-delay: 300ms</td>\n </tr>\n <tr>\n <td>animate-delay-400</td>\n <td>animation-delay: 400ms</td>\n </tr>\n <tr>\n <td>animate-delay-500</td>\n <td>animation-delay: 500ms</td>\n </tr>\n <tr>\n <td>animate-delay-700</td>\n <td>animation-delay: 700ms</td>\n </tr>\n <tr>\n <td>animate-delay-1000</td>\n <td>animation-delay: 1000ms</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Iteration Count</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-infinite</td>\n <td>animation-iteration-count: infinite</td>\n </tr>\n <tr>\n <td>animate-once</td>\n <td>animation-iteration-count: 1</td>\n </tr>\n <tr>\n <td>animate-twice</td>\n <td>animation-iteration-count: 2</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Direction</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-normal</td>\n <td>animation-direction: normal</td>\n </tr>\n <tr>\n <td>animate-reverse</td>\n <td>animation-direction: reverse</td>\n </tr>\n <tr>\n <td>animate-alternate</td>\n <td>animation-direction: alternate</td>\n </tr>\n <tr>\n <td>animate-alternate-reverse</td>\n <td>animation-direction: alternate-reverse</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Timing Function</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-ease-linear</td>\n <td>animation-timing-function: linear</td>\n </tr>\n <tr>\n <td>animate-ease-in</td>\n <td>animation-timing-function: cubic-bezier(0.4, 0, 1, 1)</td>\n </tr>\n <tr>\n <td>animate-ease-out</td>\n <td>animation-timing-function: cubic-bezier(0, 0, 0.2, 1)</td>\n </tr>\n <tr>\n <td>animate-ease-in-out</td>\n <td>animation-timing-function: cubic-bezier(0.4, 0, 0.2, 1)</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Fill Mode</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-fill-none</td>\n <td>animation-fill-mode: normal</td>\n </tr>\n <tr>\n <td>animate-fill-forwards</td>\n <td>animation-fill-mode: forwards</td>\n </tr>\n <tr>\n <td>animate-fill-backwards</td>\n <td>animation-fill-mode: backwards</td>\n </tr>\n <tr>\n <td>animate-fill-both</td>\n <td>animation-fill-mode: both</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Play State</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-running</td>\n <td>animation-play-state: running</td>\n </tr>\n <tr>\n <td>animate-paused</td>\n <td>animation-play-state: paused</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Backface Visibility State</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>backface-visible</td>\n <td>backface-visibility: visible</td>\n </tr>\n <tr>\n <td>backface-hidden</td>\n <td>backface-visibility: hidden</td>\n </tr>\n </tbody>\n </table>\n </div>\n `,\n standalone: true,\n imports: [SelectModule, FormsModule]\n})\nexport class TailwindAnimationsDemo implements OnInit {\n animation: any = null;\n\n ngOnInit() {\n this.animations = [\n 'fadein',\n 'fadeout',\n 'slideup',\n 'scalein',\n 'fadeinleft',\n 'fadeoutleft',\n 'fadeinright',\n 'fadeoutright',\n 'fadeinup',\n 'fadeoutup',\n 'width',\n 'flipup',\n 'flipleft',\n 'flipright',\n 'zoomin',\n 'zoomindown',\n 'zoominleft',\n 'zoominright',\n 'zoominup'\n ];\n }\n}"
44230
- }
44215
+ "id": "overview",
44216
+ "label": "Overview",
44217
+ "description": "Tailwind CSS is a popular CSS framework based on a utility-first design. The core provides flexible CSS classes with predefined CSS rules to build your own UI elements. For example, instead of an opinionated `btn` class as in\nBootstrap, Tailwind offers primitive classes like `bg-blue-500`, `rounded` and `p-4` to apply a button. A set of reusable classes can also be grouped as a Tailwind CSS component and there are even a couple of libraries\nthat take this approach to build components specifically for Tailwind.\n\nTailwind is an outstanding CSS library, however it lacks a true comprehensive UI suite when combined with Angular, this is where ExhaustiveUI comes in by providing a wide range of highly accessible and feature rich UI component\nlibrary. The core of ExhaustiveUI does not depend on Tailwind CSS.",
44218
+ "examples": null
44231
44219
  },
44232
44220
  {
44233
- "id": "colorpalette",
44234
- "label": "Colorpalette",
44235
- "description": "ExhaustiveUI color palette as utility classes.",
44236
- "examples": {
44237
- "typescript": "import { Component } from '@angular/core';\n\n@Component({\n template: `\n <div class=\"card\">\n <div class=\"flex flex-col gap-12\">\n <ul class=\"p-0 m-0 list-none flex sm:flex-col gap-4 flex-wrap sm:flex-nowrap\">\n <li *ngFor=\"let color of colors; let i = index\" [ngStyle]=\"{ 'min-width': '6rem' }\" class=\"flex-auto\">\n <span class=\"font-medium capitalize block mb-2 text-center sm:text-left\">{{ color }}</span>\n <div class=\"flex gap-4 flex-auto flex-col sm:flex-row\">\n <div *ngFor=\"let shade of shades\" [ngClass]=\"{ invisible: color === 'primary' && shade === 0 }\" class=\"flex flex-col items-center gap-1 flex-1\">\n <div class=\"rounded-sm h-8 w-full\" [ngStyle]=\"{ 'background-color': 'var(--p-' + color + '-' + shade + ')' }\"></div>\n <span class=\"text-sm text-surface-500 dark:text-surface-400 font-medium\">{{ shade }}</span>\n </div>\n </div>\n </li>\n </ul>\n <div class=\"flex gap-6 flex-wrap\">\n <div class=\"rounded-border p-4 border border-transparent flex items-center justify-center bg-primary hover:bg-primary-emphasis text-primary-contrast font-medium flex-auto transition-colors\">primary</div>\n <div class=\"rounded-border p-4 border border-transparent flex items-center justify-center bg-highlight hover:bg-highlight-emphasis font-medium flex-auto transition-colors\">highlight</div>\n <div class=\"rounded-border p-4 border border-surface flex items-center justify-center text-muted-color hover:text-color hover:bg-emphasis font-medium flex-auto transition-colors\">box</div>\n </div>\n </div>\n </div>\n `,\n standalone: true,\n imports: []\n})\nexport class TailwindColorpaletteDemo {\n shades: number[] = [0, 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, 950];\n colors: string[] = ['primary', 'surface'];\n}"
44238
- }
44221
+ "id": "plugin",
44222
+ "label": "Plugin",
44223
+ "description": "The [@exhaustive-ui/tailwindcss](https://www.npmjs.com/package/@exhaustive-ui/tailwindcss) is a plugin to provide first class integration between ExhaustiveUI and Tailwind CSS. It\nis designed to work both in styled and unstyled modes. In styled mode, for instance the semantic colors such as primary and surfaces are provided as Tailwind utilities e.g. `bg-primary`, `text-surface-500`,\n`text-muted-color`.\n\nIf you haven't already done so, start by integrating Tailwind into your project. Detailed steps for this process can be found in the Tailwind\n[documentation](https://tailwindcss.com/). After successfully installing Tailwind, proceed with the installation of the ExhaustiveUiTailwind plugin. This single npm package comes\nwith two libraries: the CSS version is compatible with Tailwind v4, the recommended version, while the JS version is designed for Tailwind v3.\n\n### Tailwind v4\n\nIn the CSS file that contains the tailwindcss import, add the `@exhaustive-ui/tailwindcss` import as well.\n\nFor a comprehensive starter guide, review the [ExhaustiveUI](https://github.com/e-xiste/exhaustive-ui) repository which demonstrates the integration.\n\n### Tailwind v3\n\nUse the plugins option in your Tailwind config file to configure the plugin.",
44224
+ "examples": null
44225
+ },
44226
+ {
44227
+ "id": "extensions",
44228
+ "label": "Extensions",
44229
+ "description": "The plugin extends the default configuration with a new set of utilities. All variants and breakpoints are supported e.g.\n`dark:sm:hover:bg-primary`.\n\n### Color Palette\n\nClass\nProperty\nprimary-[50-950]\nPrimary color palette.\nsurface-[0-950]\nSurface color palette.\nprimary\nDefault primary color.\nprimary-contrast\nDefault primary contrast color.\nprimary-emphasis\nDefault primary emphasis color.\nborder-surface\nDefault primary emphasis color.\nbg-emphasis\nEmphasis background e.g. hovered element.\nbg-highlight\nHighlight background.\nbg-highlight-emphasis\nHighlight background with emphasis.\nrounded-border\nBorder radius.\ntext-color\nText color with emphasis.\ntext-color-emphasis\nDefault primary emphasis color.\ntext-muted-color\nSecondary text color.\ntext-muted-color-emphasis\nSecondary text color with emphasis.",
44230
+ "examples": null
44239
44231
  },
44240
44232
  {
44241
44233
  "id": "darkmode",
44242
- "label": "Darkmode",
44243
- "description": "In styled mode, ExhaustiveUI uses the system as the default darkModeSelector in theme configuration. If you have a dark mode switch in your application, ensure that darkModeSelector is aligned with the Tailwind dark variant for seamless integration. Note that, this particular configuration isn't required if you're utilizing the default system color scheme. Suppose that, the darkModeSelector is set as my-app-dark in ExhaustiveUI. Tailwind v4 Add a custom variant for dark with a custom selector. Tailwind v3 Use the plugins option in your Tailwind config file to configure the plugin.",
44234
+ "label": "Dark Mode",
44235
+ "description": "In styled mode, ExhaustiveUI uses the `system` as the default `darkModeSelector` in theme configuration. If you have a dark mode switch in your application, ensure that `darkModeSelector` is aligned with the Tailwind\ndark variant for seamless integration. Note that, this particular configuration isn't required if you're utilizing the default system color scheme.\n\nSuppose that, the darkModeSelector is set as `my-app-dark` in ExhaustiveUI.\n\n### Tailwind v4\n\nAdd a custom variant for dark with a custom selector.\n\n### Tailwind v3\n\nUse the plugins option in your Tailwind config file to configure the plugin.",
44244
44236
  "examples": null
44245
44237
  },
44246
44238
  {
44247
- "id": "extensions",
44248
- "label": "Extensions",
44249
- "description": "The plugin extends the default configuration with a new set of utilities. All variants and breakpoints are supported e.g. dark:sm:hover:bg-primary . Color Palette Class Property primary-[50-950] Primary color palette. surface-[0-950] Surface color palette. primary Default primary color. primary-contrast Default primary contrast color. primary-emphasis Default primary emphasis color. border-surface Default primary emphasis color. bg-emphasis Emphasis background e.g. hovered element. bg-highlight Highlight background. bg-highlight-emphasis Highlight background with emphasis. rounded-border Border radius. text-color Text color with emphasis. text-color-emphasis Default primary emphasis color. text-muted-color Secondary text color. text-muted-color-emphasis Secondary text color with emphasis.",
44239
+ "id": "override",
44240
+ "label": "Override",
44241
+ "description": "Tailwind utilities may not be able to override the default styling of components due to css specificity, there are two possible solutions; Import and CSS Layer.\n\n### Important\n\nUse the `!` important modifier to enforce the styling: Tailwind v4 places it at the end of the class name, Tailwind v3 at the start. This is not the recommend approach, and should be used as last resort to avoid adding\nunnecessary style classes to your bundle.\n\nTailwind v4\n\nTailwind v3\n\n### CSS Layer\n\nCSS Layer provides control over the css specificity so that Tailwind utilities can safely override components.\n\nTailwind v4\n\nEnsure `exhaustive` layer is after `theme` and `base`, but before the other Tailwind layers such as `utilities`.\n\nNo change in the CSS configuration is required.\n\nTailwind v3\n\nThe `exhaustive` layer should be between base and utilities.\n\nTailwind v3 does not use native `layer` so needs to be defined with CSS.",
44250
44242
  "examples": null
44251
44243
  },
44244
+ {
44245
+ "id": "color-palette",
44246
+ "label": "Color Palette",
44247
+ "description": "ExhaustiveUI color palette as utility classes.",
44248
+ "examples": {
44249
+ "typescript": "import { Component } from '@angular/core';\n\n@Component({\n template: `\n <div class=\"card\">\n <div class=\"flex flex-col gap-12\">\n <ul class=\"p-0 m-0 list-none flex sm:flex-col gap-4 flex-wrap sm:flex-nowrap\">\n <li *ngFor=\"let color of colors; let i = index\" [ngStyle]=\"{ 'min-width': '6rem' }\" class=\"flex-auto\">\n <span class=\"font-medium capitalize block mb-2 text-center sm:text-left\">{{ color }}</span>\n <div class=\"flex gap-4 flex-auto flex-col sm:flex-row\">\n <div *ngFor=\"let shade of shades\" [ngClass]=\"{ invisible: color === 'primary' && shade === 0 }\" class=\"flex flex-col items-center gap-1 flex-1\">\n <div class=\"rounded-sm h-8 w-full\" [ngStyle]=\"{ 'background-color': 'var(--p-' + color + '-' + shade + ')' }\"></div>\n <span class=\"text-sm text-surface-500 dark:text-surface-400 font-medium\">{{ shade }}</span>\n </div>\n </div>\n </li>\n </ul>\n <div class=\"flex gap-6 flex-wrap\">\n <div class=\"rounded-border p-4 border border-transparent flex items-center justify-center bg-primary hover:bg-primary-emphasis text-primary-contrast font-medium flex-auto transition-colors\">primary</div>\n <div class=\"rounded-border p-4 border border-transparent flex items-center justify-center bg-highlight hover:bg-highlight-emphasis font-medium flex-auto transition-colors\">highlight</div>\n <div class=\"rounded-border p-4 border border-surface flex items-center justify-center text-muted-color hover:text-color hover:bg-emphasis font-medium flex-auto transition-colors\">box</div>\n </div>\n </div>\n </div>\n `,\n standalone: true,\n imports: []\n})\nexport class TailwindColorpaletteDemo {\n shades: number[] = [0, 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, 950];\n colors: string[] = ['primary', 'surface'];\n}"
44250
+ }
44251
+ },
44252
44252
  {
44253
44253
  "id": "form",
44254
44254
  "label": "Form",
@@ -44266,22 +44266,12 @@
44266
44266
  }
44267
44267
  },
44268
44268
  {
44269
- "id": "override",
44270
- "label": "Override",
44271
- "description": "Tailwind utilities may not be able to override the default styling of components due to css specificity, there are two possible solutions; Import and CSS Layer. Important Use the ! important modifier to enforce the styling: Tailwind v4 places it at the end of the class name, Tailwind v3 at the start. This is not the recommend approach, and should be used as last resort to avoid adding unnecessary style classes to your bundle. Tailwind v4 Tailwind v3 CSS Layer CSS Layer provides control over the css specificity so that Tailwind utilities can safely override components. Tailwind v4 Ensure exhaustive layer is after theme and base , but before the other Tailwind layers such as utilities . No change in the CSS configuration is required. Tailwind v3 The exhaustive layer should be between base and utilities. Tailwind v3 does not use native layer so needs to be defined with CSS.",
44272
- "examples": null
44273
- },
44274
- {
44275
- "id": "overview",
44276
- "label": "Overview",
44277
- "description": "Tailwind CSS is a popular CSS framework based on a utility-first design. The core provides flexible CSS classes with predefined CSS rules to build your own UI elements. For example, instead of an opinionated btn class as in Bootstrap, Tailwind offers primitive classes like bg-blue-500 , rounded and p-4 to apply a button. A set of reusable classes can also be grouped as a Tailwind CSS component and there are even a couple of libraries that take this approach to build components specifically for Tailwind. Tailwind is an outstanding CSS library, however it lacks a true comprehensive UI suite when combined with Angular, this is where ExhaustiveUI comes in by providing a wide range of highly accessible and feature rich UI component library. The core of ExhaustiveUI does not depend on Tailwind CSS.",
44278
- "examples": null
44279
- },
44280
- {
44281
- "id": "plugin",
44282
- "label": "Plugin",
44283
- "description": "The @exhaustive-ui/tailwindcss is a plugin to provide first class integration between ExhaustiveUI and Tailwind CSS. It is designed to work both in styled and unstyled modes. In styled mode, for instance the semantic colors such as primary and surfaces are provided as Tailwind utilities e.g. bg-primary , text-surface-500 , text-muted-color . If you haven't already done so, start by integrating Tailwind into your project. Detailed steps for this process can be found in the Tailwind documentation . After successfully installing Tailwind, proceed with the installation of the ExhaustiveUiTailwind plugin. This single npm package comes with two libraries: the CSS version is compatible with Tailwind v4, the recommended version, while the JS version is designed for Tailwind v3. Tailwind v4 In the CSS file that contains the tailwindcss import, add the @exhaustive-ui/tailwindcss import as well. For a comprehensive starter guide, review the ExhaustiveUI repository which demonstrates the integration. Tailwind v3 Use the plugins option in your Tailwind config file to configure the plugin.",
44284
- "examples": null
44269
+ "id": "animations",
44270
+ "label": "Animations",
44271
+ "description": "The plugin also adds extended animation utilities that can be used with the styleclass and animateonscroll directives.",
44272
+ "examples": {
44273
+ "typescript": "import { Component, OnInit } from '@angular/core';\nimport { FormsModule } from '@angular/forms';\nimport { SelectModule } from '@exhaustive-ui/core/select';\n\n@Component({\n template: `\n <div class=\"card\">\n <p-select [(ngModel)]=\"animation\" [options]=\"animations\" placeholder=\"Select One\" class=\"w-full sm:w-44\" />\n <div class=\"py-8 overflow-hidden\">\n <div [ngClass]=\"dynamicAnimationClasses\"></div>\n </div>\n </div>\n <h3>Animations</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-fadein</td>\n <td>fadein 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeout</td>\n <td>fadeout 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-slidedown</td>\n <td>slidedown 0.45s ease-in-out</td>\n </tr>\n <tr>\n <td>animate-slideup</td>\n <td>slideup 0.45s cubic-bezier(0, 1, 0, 1)</td>\n </tr>\n <tr>\n <td>animate-scalein</td>\n <td>scalein 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeinleft</td>\n <td>fadeinleft 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutleft</td>\n <td>fadeoutleft 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeinright</td>\n <td>fadeinright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutright</td>\n <td>fadeoutright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeinup</td>\n <td>fadeinup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutup</td>\n <td>fadeoutup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeindown</td>\n <td>fadeindown 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-fadeoutup</td>\n <td>fadeoutup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-width</td>\n <td>width 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flip</td>\n <td>flip 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flipup</td>\n <td>flipup 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flipleft</td>\n <td>fadein 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-flipright</td>\n <td>flipright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoomin</td>\n <td>zoomin 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoomindown</td>\n <td>zoomindown 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoominleft</td>\n <td>zoominleft 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoominright</td>\n <td>zoominright 0.15s linear</td>\n </tr>\n <tr>\n <td>animate-zoominup</td>\n <td>zoominup 0.15s linear</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Animation Duration</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-duration-0</td>\n <td>animation-duration: 0s</td>\n </tr>\n <tr>\n <td>animate-duration-75</td>\n <td>animation-duration: 75ms</td>\n </tr>\n <tr>\n <td>animate-duration-100</td>\n <td>animation-duration: 100ms</td>\n </tr>\n <tr>\n <td>animate-duration-200</td>\n <td>animation-duration: 200ms</td>\n </tr>\n <tr>\n <td>animate-duration-300</td>\n <td>animation-duration: 300ms</td>\n </tr>\n <tr>\n <td>animate-duration-400</td>\n <td>animation-duration: 400ms</td>\n </tr>\n <tr>\n <td>animate-duration-500</td>\n <td>animation-duration: 500ms</td>\n </tr>\n <tr>\n <td>animate-duration-700</td>\n <td>animation-duration: 700ms</td>\n </tr>\n <tr>\n <td>animate-duration-1000</td>\n <td>animation-duration: 1000ms</td>\n </tr>\n <tr>\n <td>animate-duration-2000</td>\n <td>animation-duration: 2000ms</td>\n </tr>\n <tr>\n <td>animate-duration-3000</td>\n <td>animation-duration: 300ms</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Animation Delay</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-delay-none</td>\n <td>animation-duration: 0s</td>\n </tr>\n <tr>\n <td>animate-delay-75</td>\n <td>animation-delay: 75ms</td>\n </tr>\n <tr>\n <td>animate-delay-100</td>\n <td>animation-delay: 100ms</td>\n </tr>\n <tr>\n <td>animate-delay-150</td>\n <td>animation-delay: 150ms</td>\n </tr>\n <tr>\n <td>animate-delay-200</td>\n <td>animation-delay: 200ms</td>\n </tr>\n <tr>\n <td>animate-delay-300</td>\n <td>animation-delay: 300ms</td>\n </tr>\n <tr>\n <td>animate-delay-400</td>\n <td>animation-delay: 400ms</td>\n </tr>\n <tr>\n <td>animate-delay-500</td>\n <td>animation-delay: 500ms</td>\n </tr>\n <tr>\n <td>animate-delay-700</td>\n <td>animation-delay: 700ms</td>\n </tr>\n <tr>\n <td>animate-delay-1000</td>\n <td>animation-delay: 1000ms</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Iteration Count</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-infinite</td>\n <td>animation-iteration-count: infinite</td>\n </tr>\n <tr>\n <td>animate-once</td>\n <td>animation-iteration-count: 1</td>\n </tr>\n <tr>\n <td>animate-twice</td>\n <td>animation-iteration-count: 2</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Direction</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-normal</td>\n <td>animation-direction: normal</td>\n </tr>\n <tr>\n <td>animate-reverse</td>\n <td>animation-direction: reverse</td>\n </tr>\n <tr>\n <td>animate-alternate</td>\n <td>animation-direction: alternate</td>\n </tr>\n <tr>\n <td>animate-alternate-reverse</td>\n <td>animation-direction: alternate-reverse</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Timing Function</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-ease-linear</td>\n <td>animation-timing-function: linear</td>\n </tr>\n <tr>\n <td>animate-ease-in</td>\n <td>animation-timing-function: cubic-bezier(0.4, 0, 1, 1)</td>\n </tr>\n <tr>\n <td>animate-ease-out</td>\n <td>animation-timing-function: cubic-bezier(0, 0, 0.2, 1)</td>\n </tr>\n <tr>\n <td>animate-ease-in-out</td>\n <td>animation-timing-function: cubic-bezier(0.4, 0, 0.2, 1)</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Fill Mode</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-fill-none</td>\n <td>animation-fill-mode: normal</td>\n </tr>\n <tr>\n <td>animate-fill-forwards</td>\n <td>animation-fill-mode: forwards</td>\n </tr>\n <tr>\n <td>animate-fill-backwards</td>\n <td>animation-fill-mode: backwards</td>\n </tr>\n <tr>\n <td>animate-fill-both</td>\n <td>animation-fill-mode: both</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Play State</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>animate-running</td>\n <td>animation-play-state: running</td>\n </tr>\n <tr>\n <td>animate-paused</td>\n <td>animation-play-state: paused</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h3>Backface Visibility State</h3>\n <div class=\"doc-tablewrapper\">\n <table class=\"doc-table\">\n <thead>\n <tr>\n <th>Class</th>\n <th>Property</th>\n </tr>\n </thead>\n <tbody>\n <tr>\n <td>backface-visible</td>\n <td>backface-visibility: visible</td>\n </tr>\n <tr>\n <td>backface-hidden</td>\n <td>backface-visibility: hidden</td>\n </tr>\n </tbody>\n </table>\n </div>\n `,\n standalone: true,\n imports: [SelectModule, FormsModule]\n})\nexport class TailwindAnimationsDemo implements OnInit {\n animation: any = null;\n\n ngOnInit() {\n this.animations = [\n 'fadein',\n 'fadeout',\n 'slideup',\n 'scalein',\n 'fadeinleft',\n 'fadeoutleft',\n 'fadeinright',\n 'fadeoutright',\n 'fadeinup',\n 'fadeoutup',\n 'width',\n 'flipup',\n 'flipleft',\n 'flipright',\n 'zoomin',\n 'zoomindown',\n 'zoominleft',\n 'zoominright',\n 'zoominup'\n ];\n }\n}"
44274
+ }
44285
44275
  }
44286
44276
  ]
44287
44277
  },
@@ -44292,43 +44282,39 @@
44292
44282
  "description": "LLM-optimized documentation endpoints for ExhaustiveUI components.",
44293
44283
  "sections": [
44294
44284
  {
44295
- "id": "agentskill",
44296
- "label": "Agentskill",
44297
- "description": "The markdown files above are also bundled as an Agent Skill , the SKILL.md format supported by coding agents such as Claude Code, Codex, Cursor and OpenCode. Once installed, the agent reads the component docs, API tables and guides from disk whenever it works on ExhaustiveUI code, instead of fetching them from this site each time. Install it with the skills CLI , which asks which agents to set it up for. By default the skill is installed into the current project, so your team gets it too. Add -g to install it for your user instead. You can also download the zip and extract it into a folder named exhaustive-ui in your agent's skills directory.",
44298
- "examples": {
44299
- "command": "npx skills add https://exhaustive-ui.com\n\n# update to the latest docs\nnpx skills update exhaustive-ui"
44300
- }
44285
+ "id": "llmstxt",
44286
+ "label": "/llms.txt",
44287
+ "description": "The [llms.txt](https://llmstxt.org/) file is an industry standard that helps AI models better understand and navigate the ExhaustiveUI documentation. It lists key pages in a\nstructured format, making it easier for LLMs to retrieve relevant information.\n\n[\n\n](/llms/llms.txt)",
44288
+ "examples": null
44301
44289
  },
44302
44290
  {
44303
44291
  "id": "llmsfulltxt",
44304
- "label": "Llmsfulltxt",
44305
- "description": "The llms-full.txt file is a complete list of all the pages in the ExhaustiveUI documentation. It is used to help AI models understand the entire documentation set.",
44292
+ "label": "/llms-full.txt",
44293
+ "description": "The `llms-full.txt` file is a complete list of all the pages in the ExhaustiveUI documentation. It is used to help AI models understand the entire documentation set.\n\n[\n\n](/llms/llms-full.txt)",
44306
44294
  "examples": null
44307
44295
  },
44308
44296
  {
44309
- "id": "llmstxt",
44310
- "label": "Llmstxt",
44311
- "description": "The llms.txt file is an industry standard that helps AI models better understand and navigate the ExhaustiveUI documentation. It lists key pages in a structured format, making it easier for LLMs to retrieve relevant information.",
44297
+ "id": "markdown",
44298
+ "label": ".md extension",
44299
+ "description": "Add a `.md` to a page's URL to display a Markdown version of that page.\n\n[\n\n](/llms/components/button.md)",
44312
44300
  "examples": null
44313
44301
  },
44314
44302
  {
44315
- "id": "manifest",
44316
- "label": "Manifest",
44317
- "description": "/llms/manifest.json describes every component, directive, NgModule, service and exported type as structured data, for tools that need exact facts rather than prose: MCP servers, code generators, linters and design tool integrations. It is generated from the Angular metadata in the compiled library, so selectors and inputs match what the compiler accepts. Each entry point lists its import path, NgModule, services and exported types. Each component or directive lists its selector, inputs with type, allowed values, default, transform and two-way binding, outputs with payload type, templates with their context type, methods, forms support and pass-through keys.",
44318
- "examples": {
44319
- "typescript": "{\n \"schemaVersion\": 1,\n \"entryPoints\": [\n {\n \"name\": \"button\",\n \"import\": \"@exhaustive-ui/core/button\",\n \"modules\": [\"ButtonModule\"],\n \"declarations\": [\n {\n \"kind\": \"component\",\n \"className\": \"Button\",\n \"selector\": \"p-button\",\n \"inputs\": [\n { \"name\": \"severity\", \"type\": \"ButtonSeverity\", \"values\": [\"success\", \"info\", \"warn\", \"danger\", \"secondary\", \"contrast\", \"help\", \"primary\"] },\n { \"name\": \"raised\", \"type\": \"boolean\", \"default\": \"false\", \"transform\": \"booleanAttribute\" }\n ],\n \"outputs\": [{ \"name\": \"onClick\", \"payload\": \"MouseEvent\" }],\n \"templates\": [{ \"name\": \"icon\", \"context\": \"ButtonIconTemplateContext\" }]\n }\n ]\n }\n ]\n}"
44320
- }
44303
+ "id": "agentskill",
44304
+ "label": "Agent Skill",
44305
+ "description": "The markdown files above are also bundled as an [Agent Skill](https://agentskills.io), the `SKILL.md` format supported by coding agents such as Claude Code,\nCodex, Cursor and OpenCode. Once installed, the agent reads the component docs, API tables and guides from disk whenever it works on ExhaustiveUI code, instead of fetching them from this site each time.\n\nInstall it with the [skills CLI](https://skills.sh/docs/cli), which asks which agents to set it up for.\n\n```bash\nnpx skills add https://exhaustive-ui.com\n\n# update to the latest docs\nnpx skills update exhaustive-ui\n```\n\nBy default the skill is installed into the current project, so your team gets it too. Add `-g` to install it for your user instead. You can also download the zip and extract it into a folder named `exhaustive-ui` in your\nagent's skills directory.\n\n[\n\n](/llms/exhaustive-ui-skill.zip)",
44306
+ "examples": null
44321
44307
  },
44322
44308
  {
44323
- "id": "markdownextension",
44324
- "label": "Markdownextension",
44325
- "description": "Add a .md to a page's URL to display a Markdown version of that page.",
44309
+ "id": "mcp",
44310
+ "label": "MCP Server",
44311
+ "description": "[@exhaustive-ui/mcp](https://www.npmjs.com/package/@exhaustive-ui/mcp) is a\n[Model Context Protocol](https://modelcontextprotocol.io) server that gives coding agents such as Claude Code, Cursor, Claude Desktop, VS Code Copilot and Codex\ntools to query this documentation instead of guessing from PrimeNG memory: list and search components, read a component's docs and API, fetch a complete code example, read the setup guides, and validate an Angular template against the\ncompiled API (unknown inputs or outputs, invalid literal values, unsupported two-way bindings, deprecated inputs, PrimeNG imports and selectors).\n\nThe server reads the files described on this page from the live site, so it always reflects the deployed documentation without reinstalling the package, and keeps them in memory for 15 minutes. A snapshot of the same files is bundled\nin the package and used when the network is unavailable.\n\nRegister it with Claude Code:\n\n```bash\nclaude mcp add exhaustive-ui -s user -- npx -y @exhaustive-ui/mcp\n```\n\nOr add it to the MCP configuration of your client (`.cursor/mcp.json`, `claude_desktop_config.json`, `.vscode/mcp.json` with a `servers` key, ...):\n\n```typescript\n{\n \"mcpServers\": {\n \"exhaustive-ui\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@exhaustive-ui/mcp\"]\n }\n }\n}\n```\n\nThe server exposes the `list`, `search`, `get_component`, `get_guide`, `get_example`, `get_setup`, `validate_usage` and `version` tools, the Markdown files of this page as MCP resources, and\nprompts for the usual tasks (use a component, build a form, theme a component, migrate from PrimeNG, audit usage). Set `EXHAUSTIVE_UI_DOCS_URL` to read another deployment of the docs, for instance a local `ng serve`, and\n`EXHAUSTIVE_UI_MCP_OFFLINE=1` to only use the bundled snapshot. The package README lists every option.",
44326
44312
  "examples": null
44327
44313
  },
44328
44314
  {
44329
- "id": "mcp",
44330
- "label": "Mcp",
44331
- "description": "@exhaustive-ui/mcp is a Model Context Protocol server that gives coding agents such as Claude Code, Cursor, Claude Desktop, VS Code Copilot and Codex tools to query this documentation instead of guessing from PrimeNG memory: list and search components, read a component's docs and API, fetch a complete code example, read the setup guides, and validate an Angular template against the compiled API (unknown inputs or outputs, invalid literal values, unsupported two-way bindings, deprecated inputs, PrimeNG imports and selectors). The server reads the files described on this page from the live site, so it always reflects the deployed documentation without reinstalling the package, and keeps them in memory for 15 minutes. A snapshot of the same files is bundled in the package and used when the network is unavailable. Register it with Claude Code: Or add it to the MCP configuration of your client ( .cursor/mcp.json , claude_desktop_config.json , .vscode/mcp.json with a servers key, ...): The server exposes the list , search , get_component , get_guide , get_example , get_setup , validate_usage and version tools, the Markdown files of this page as MCP resources, and prompts for the usual tasks (use a component, build a form, theme a component, migrate from PrimeNG, audit usage). Set EXHAUSTIVE_UI_DOCS_URL to read another deployment of the docs, for instance a local ng serve , and EXHAUSTIVE_UI_MCP_OFFLINE=1 to only use the bundled snapshot. The package README lists every option.",
44315
+ "id": "manifest",
44316
+ "label": "Manifest",
44317
+ "description": "[/llms/manifest.json](/llms/manifest.json) describes every component, directive, NgModule, service and exported type as structured data, for tools that need exact facts rather than prose:\nMCP servers, code generators, linters and design tool integrations. It is generated from the Angular metadata in the compiled library, so selectors and inputs match what the compiler accepts.\n\nEach entry point lists its import path, NgModule, services and exported types. Each component or directive lists its selector, inputs with type, allowed values, default, transform and two-way binding, outputs with payload type,\ntemplates with their context type, methods, forms support and pass-through keys.\n\n```typescript\n{\n \"schemaVersion\": 1,\n \"entryPoints\": [\n {\n \"name\": \"button\",\n \"import\": \"@exhaustive-ui/core/button\",\n \"modules\": [\"ButtonModule\"],\n \"declarations\": [\n {\n \"kind\": \"component\",\n \"className\": \"Button\",\n \"selector\": \"p-button\",\n \"inputs\": [\n { \"name\": \"severity\", \"type\": \"ButtonSeverity\", \"values\": [\"success\", \"info\", \"warn\", \"danger\", \"secondary\", \"contrast\", \"help\", \"primary\"] },\n { \"name\": \"raised\", \"type\": \"boolean\", \"default\": \"false\", \"transform\": \"booleanAttribute\" }\n ],\n \"outputs\": [{ \"name\": \"onClick\", \"payload\": \"MouseEvent\" }],\n \"templates\": [{ \"name\": \"icon\", \"context\": \"ButtonIconTemplateContext\" }]\n }\n ]\n }\n ]\n}\n```",
44332
44318
  "examples": null
44333
44319
  }
44334
44320
  ]
@@ -44342,37 +44328,37 @@
44342
44328
  {
44343
44329
  "id": "colors",
44344
44330
  "label": "Colors",
44345
- "description": "Colors on a web page should aim a contrast ratio of at least 4.5:1 and consider a selection of colors that do not cause vibration. Good Contrast Color contrast between the background and the foreground content should be sufficient enough to ensure readability. Example below displays two cases with good and bad samples. GOOD BAD Vibration Color vibration is leads to an illusion of motion due to choosing colors that have low visibility against each other. Color combinations need to be picked with caution to avoid vibration. VIBRATE Dark Mode Highly saturated colors should be avoided when used within a dark design scheme as they cause eye strain. Instead desaturated colors should be preferred. Indigo 500 Indigo 200",
44331
+ "description": "Colors on a web page should aim a contrast ratio of at least **4.5:1** and consider a selection of colors that do not cause vibration.\n\n### Good Contrast\n\nColor contrast between the background and the foreground content should be sufficient enough to ensure readability. Example below displays two cases with good and bad samples.\n\nGOOD\nBAD\n\n### Vibration\n\nColor vibration is leads to an illusion of motion due to choosing colors that have low visibility against each other. Color combinations need to be picked with caution to avoid vibration.\n\nVIBRATE\n\n### Dark Mode\n\nHighly saturated colors should be avoided when used within a dark design scheme as they cause eye strain. Instead desaturated colors should be preferred.\n\nIndigo 500\nIndigo 200",
44346
44332
  "examples": null
44347
44333
  },
44348
44334
  {
44349
44335
  "id": "formcontrols",
44350
44336
  "label": "Formcontrols",
44351
- "description": "Native form elements should be preferred instead of elements that are meant for other purposes like presentation. As an example, button below is rendered as a form control by the browser, can receive focus via tabbing and can be used with space key as well to trigger. On the other hand, a fancy css based button using a div has no keyboard or screen reader support. tabindex is required to make a div element accessible in addition to use a keydown to bring the keyboard support back. To avoid the overload and implementing functionality that is already provided by the browser, native form controls should be preferred. Relations Form components must be related to another element that describes what the form element is used for. This is usually achieved with the label element.",
44337
+ "description": "Native form elements should be preferred instead of elements that are meant for other purposes like presentation. As an example, button below is rendered as a form control by the browser, can receive focus via tabbing and can be used\nwith space key as well to trigger.\n\n```html\n<button (click)=\"onButtonClick($event)\">Click></button>\n```\n\nOn the other hand, a fancy css based button using a div has no keyboard or screen reader support.\n\n```html\n<div class=\"fancy-button\" (click)=\"onButtonClick($event)\">Click</div>\n```\n\n`tabindex` is required to make a div element accessible in addition to use a keydown to bring the keyboard support back. To avoid the overload and implementing functionality that is already provided by the browser, native form\ncontrols should be preferred.\n\n```html\n<div class=\"fancy-button\" (click)=\"onButtonClick($event)\" (keydown)=\"onKeyDown($event)\" tabIndex=\"0\">Click</div>\n```\n\n### Relations\n\nForm components must be related to another element that describes what the form element is used for. This is usually achieved with the `label` element.\n\n```html\n<label for=\"myinput\">Username:</label>\n<input id=\"myinput\" type=\"text\" name=\"username\" />\n```",
44352
44338
  "examples": null
44353
44339
  },
44354
44340
  {
44355
44341
  "id": "introduction",
44356
44342
  "label": "Introduction",
44357
- "description": "According to the World Health Organization, 15% of the world population has a disability to some degree. As a result, accessibility features in any context such as a ramp for wheelchair users or a multimedia with captions are crucial to ensure content can be consumed by anyone. Disabilities Types of disabilities are diverse so you need to know your audience well and how they interact with the content created. There four main categories; Visual Impairments Blindness, low-level vision or color blindness are the common types of visual impairments. Screen magnifiers and the color blind mode are usually built-in features of the browsers whereas for people who rely on screen readers, page developers are required to make sure content is readable by the readers. Popular readers are NVDA , JAWS and ChromeVox . Hearing Impairments Deafness or hearing loss refers to the inability to hear sounds totally or partially. People with hearing impairments use assistive devices however it may not be enough when interacting with a web page. Common implementation is providing textual alternatives, transcripts and captions for content with audio. Mobility Impairments People with mobility impairments have disabilities related to movement due to loss of a limb, paralysis or other varying reasons. Assistive technologies like a head pointer is a device to interact with a screen whereas keyboard or a trackpad remain as solutions for people who are not able to utilize a mouse. Cognitive Impairments Cognitive impairments have a wider range that includes people with learning disabilities, depression and dyslexia. A well designed content also leads to better user experience for people without disabilities so designing for cognitive impairments result in better design for any user.",
44343
+ "description": "According to the World Health Organization, 15% of the world population has a disability to some degree. As a result, accessibility features in any context such as a ramp for wheelchair users or a multimedia with captions are crucial\nto ensure content can be consumed by anyone.\n\n### Disabilities\n\nTypes of disabilities are diverse so you need to know your audience well and how they interact with the content created. There four main categories;\n\n### Visual Impairments\n\nBlindness, low-level vision or color blindness are the common types of visual impairments. Screen magnifiers and the color blind mode are usually built-in features of the browsers whereas for people who rely on screen readers, page\ndevelopers are required to make sure content is readable by the readers. Popular readers are\n[NVDA](https://www.nvaccess.org), [JAWS](https://www.freedomscientific.com/Products/software/JAWS/) and\n[ChromeVox](https://www.chromevox.com).\n\n### Hearing Impairments\n\nDeafness or hearing loss refers to the inability to hear sounds totally or partially. People with hearing impairments use assistive devices however it may not be enough when interacting with a web page. Common implementation is\nproviding textual alternatives, transcripts and captions for content with audio.\n\n### Mobility Impairments\n\nPeople with mobility impairments have disabilities related to movement due to loss of a limb, paralysis or other varying reasons. Assistive technologies like a head pointer is a device to interact with a screen whereas keyboard or a\ntrackpad remain as solutions for people who are not able to utilize a mouse.\n\n### Cognitive Impairments\n\nCognitive impairments have a wider range that includes people with learning disabilities, depression and dyslexia. A well designed content also leads to better user experience for people without disabilities so designing for cognitive\nimpairments result in better design for any user.",
44358
44344
  "examples": null
44359
44345
  },
44360
44346
  {
44361
44347
  "id": "semantichtml",
44362
44348
  "label": "Semantichtml",
44363
- "description": "HTML offers various element to organize content on a web page that screen readers are aware of. Preferring Semantic HTML for good semantics provide out of the box support for reader which is not possible when regular div elements with classes are used. Consider the following example that do not mean too much for readers. Same layout can be achieved using the semantic elements with screen reader support built-in.",
44349
+ "description": "HTML offers various element to organize content on a web page that screen readers are aware of. Preferring Semantic HTML for good semantics provide out of the box support for reader which is not possible when regular\n`div` elements with classes are used. Consider the following example that do not mean too much for readers.\n\n```html\n<div class=\"header\"/>\n <div class=\"header-text\">Header></div>\n</div>\n\n<div class=\"nav\"></div>\n\n<div class=\"main\">\n <div class=\"content\"></div>\n <div class=\"sidebar\"></div>\n</div>\n\n<div class=\"footer\"></div>\n```\n\nSame layout can be achieved using the semantic elements with screen reader support built-in.\n\n```html\n<header>\n <h1>Header</h1>\n</header>\n\n<nav></nav>\n\n<main>\n <article></article>\n <aside></aside>\n</main>\n\n<footer></footer>\n```",
44364
44350
  "examples": null
44365
44351
  },
44366
44352
  {
44367
44353
  "id": "waiaria",
44368
44354
  "label": "Waiaria",
44369
- "description": "ARIA refers to \"Accessible Rich Internet Applications\" is a suite to fill the gap where semantic HTML is inadequate. These cases are mainly related to rich UI components/widgets. Although browser support for rich UI components such as a datepicker or colorpicker has been improved over the past years many web developers still utilize UI components derived from standard HTML elements created by them or by other projects like ExhaustiveUI. These types of components must provide keyboard and screen reader support, the latter case is where the WAI-ARIA is utilized. ARIA consists of roles, properties and attributes. Roles define what the element is mainly used for e.g. checkbox , dialog , tablist whereas States and Properties define the metadata of the element like aria-checked , aria-disabled . Consider the following case of a native checkbox. It has built-in keyboard and screen reader support. A fancy checkbox with css animations might look more appealing but accessibility might be lacking. Checkbox below may display a checked font icon with animations however it is not tabbable, cannot be checked with space key and cannot be read by a reader. One alternative is using ARIA roles for readers and use javascript for keyboard support. Notice the usage of aria-labelledby as a replacement of the label tag with for. However the best practice is combining semantic HTML for accessibility while keeping the design for UX. This approach involves hiding a native checkbox for accessibility and using javascript events to update its state. Notice the usage of p-hidden-accessible that hides the elements from the user but not from the screen reader. A working sample is the ExhaustiveUI checkbox that is tabbable, keyboard accessible and is compliant with a screen reader. Instead of ARIA roles it relies on a hidden native checkbox. Remember Me",
44355
+ "description": "ARIA refers to \"Accessible Rich Internet Applications\" is a suite to fill the gap where semantic HTML is inadequate. These cases are mainly related to rich UI components/widgets. Although browser support for rich UI components such as\na datepicker or colorpicker has been improved over the past years many web developers still utilize UI components derived from standard HTML elements created by them or by other projects like ExhaustiveUI. These types of components\nmust provide keyboard and screen reader support, the latter case is where the WAI-ARIA is utilized.\n\nARIA consists of roles, properties and attributes. **Roles** define what the element is mainly used for e.g. `checkbox`, `dialog`, `tablist` whereas **States** and **Properties** define the metadata of the\nelement like `aria-checked`, `aria-disabled`.\n\nConsider the following case of a native checkbox. It has built-in keyboard and screen reader support.\n\n```html\n<input type=\"checkbox\" value=\"Prime\" name=\"ui\" checked/>\n```\n\nA fancy checkbox with css animations might look more appealing but accessibility might be lacking. Checkbox below may display a checked font icon with animations however it is not tabbable, cannot be checked with space key and cannot\nbe read by a reader.\n\n```html\n<div class=\"fancy-checkbox\">\n <i *ngIf=\"checked\" class=\"checked-icon\"></i>\n</div>\n```\n\nOne alternative is using ARIA roles for readers and use javascript for keyboard support. Notice the usage of\n`aria-labelledby` as a replacement of the `label` tag with for.\n\n```html\n<span id=\"chk-label\">Remember Me></span>\n<div class=\"fancy-checkbox\" role=\"checkbox\" aria-checked=\"false\" tabindex=\"0\" aria-labelledby=\"chk-label\" (click)=\"toggle()\" (keydown)=\"onKeyDown($event)\">\n <i *ngIf=\"checked\" class=\"checked-icon\"></i>\n</div>\n```\n\nHowever the best practice is combining semantic HTML for accessibility while keeping the design for UX. This approach involves hiding a native checkbox for accessibility and using javascript events to update its state. Notice the\nusage of\n`p-hidden-accessible`\nthat hides the elements from the user but not from the screen reader.\n\n```html\n<label for=\"chkbox\">Remember Me></label>\n<div class=\"fancy-checkbox\" (click)=\"toggle()\">\n <input class=\"p-hidden-accessible\" type=\"checkbox\" id=\"chkbox\" (focus)=\"updateParentVisuals()\" (blur)=\"updateParentVisuals()\" (keydown)=\"$event.keyCode === 32 && updateParentVisuals()\">\n <i *ngIf=\"checked\" class=\"checked-icon\"></i>\n</div>\n```\n\nA working sample is the ExhaustiveUI checkbox that is tabbable, keyboard accessible and is compliant with a screen reader. Instead of ARIA roles it relies on a hidden native checkbox.\n\nRemember Me",
44370
44356
  "examples": null
44371
44357
  },
44372
44358
  {
44373
44359
  "id": "wcag",
44374
44360
  "label": "Wcag",
44375
- "description": "WCAG refers to Web Content Accessibility Guideline , a standard managed by the WAI (Web Accessibility Initiative) of W3C (World Wide Web Consortium). WCAG consists of recommendations for making the web content more accessible. ExhaustiveUI components aim high level of WCAG compliancy in the near future. Various countries around the globe have governmental policies regarding web accessibility as well. Most well known of these are Section 508 in the US and Web Accessibility Directive of the European Union.",
44361
+ "description": "[WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/) refers to **Web Content Accessibility Guideline**, a standard managed by the WAI (Web Accessibility Initiative) of W3C (World Wide\nWeb Consortium). WCAG consists of recommendations for making the web content more accessible. ExhaustiveUI components aim high level of WCAG compliancy in the near future.\n\nVarious countries around the globe have governmental policies regarding web accessibility as well. Most well known of these are [Section 508](https://www.section508.gov/manage/laws-and-policies/) in the US and\n[Web Accessibility Directive](https://digital-strategy.ec.europa.eu/en/policies/web-accessibility) of the European Union.",
44376
44362
  "examples": null
44377
44363
  }
44378
44364
  ]
@@ -44386,19 +44372,19 @@
44386
44372
  {
44387
44373
  "id": "anchoredoverlays",
44388
44374
  "label": "Anchoredoverlays",
44389
- "description": "Anchored overlays are the components that have a floating ui positioned relatively to another element such as Select, Popover. The enter and leave animations are defined with the .p-anchored-overlay-enter-active and .p-anchored-overlay-leave-active classes.",
44375
+ "description": "Anchored overlays are the components that have a floating ui positioned relatively to another element such as Select, Popover. The enter and leave animations are defined with the `.p-anchored-overlay-enter-active` and\n`.p-anchored-overlay-leave-active`\nclasses.",
44390
44376
  "examples": null
44391
44377
  },
44392
44378
  {
44393
44379
  "id": "collapsibles",
44394
44380
  "label": "Collapsibles",
44395
- "description": "Collapsible components have a content that is toggleable including Accordion, Panel, Fieldset, Stepper and PanelMenu. The enter and leave animations are defined with the .p-collapsible-enter-active and .p-collapsible-leave-active classes. Header I Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Header II Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Consectetur, adipisci velit, sed quia non numquam eius modi. Header III Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Consectetur, adipisci velit, sed quia non numquam eius modi.",
44381
+ "description": "Collapsible components have a content that is toggleable including Accordion, Panel, Fieldset, Stepper and PanelMenu. The enter and leave animations are defined with the `.p-collapsible-enter-active` and\n`.p-collapsible-leave-active`\nclasses.\n\nHeader I\n\nLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea\ncommodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim\nid est laborum.\n\nHeader II\n\nSed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.\nNemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Consectetur, adipisci velit, sed quia non numquam eius modi.\n\nHeader III\n\nSed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.\nNemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Consectetur, adipisci velit, sed quia non numquam eius modi.",
44396
44382
  "examples": null
44397
44383
  },
44398
44384
  {
44399
44385
  "id": "dialog",
44400
44386
  "label": "Dialog",
44401
- "description": "Overlays such as Dialog and Drawer are positioned relative to the viewport and have their own animations. Update your information. Username Email",
44387
+ "description": "Overlays such as Dialog and Drawer are positioned relative to the viewport and have their own animations.\n\nUpdate your information.\nUsername\nEmail",
44402
44388
  "examples": null
44403
44389
  },
44404
44390
  {
@@ -44410,13 +44396,13 @@
44410
44396
  {
44411
44397
  "id": "introduction",
44412
44398
  "label": "Introduction",
44413
- "description": "Various ExhaustiveUI Components utilize native CSS animations to provide an enhanced user experience. The default animations are based on the best practices recommended by the usability experts. In case you need to customize the default animations, this documentation covers the entire set of built-in animations. Animations are defined using a combination of style classes and keyframes. The ⁠ .{classname}-enter-active and ⁠ .{classname}-leave-active classes specify the animation name, duration, and easing function. You can customize animations globally by overriding the default animation classes, affecting all components. Alternatively, you can apply scoped classes to individual components to modify their animations independently. For demo purposes, this second approach is used throughout the next sections.",
44399
+ "description": "Various ExhaustiveUI Components utilize native CSS animations to provide an enhanced user experience. The default animations are based on the best practices recommended by the usability experts. In case you need to customize the\ndefault animations, this documentation covers the entire set of built-in animations.\n\nAnimations are defined using a combination of style classes and keyframes. The ⁠`.{classname}-enter-active` and ⁠`.{classname}-leave-active` classes specify the animation name, duration, and easing\nfunction. You can customize animations globally by overriding the default animation classes, affecting all components. Alternatively, you can apply scoped classes to individual components to modify their animations independently. For\ndemo purposes, this second approach is used throughout the next sections.",
44414
44400
  "examples": null
44415
44401
  },
44416
44402
  {
44417
44403
  "id": "reference",
44418
44404
  "label": "Reference",
44419
- "description": "List of class names of the CSS animations used by the components. Component Enter Class Leave Class Accordion .p-collapsible-enter-active .p-collapsible-leave-active AutoComplete .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active CascadeSelect .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active ColorPicker .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active ConfirmPopup .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active ContextMenu .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active DatePicker .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active Dialog .p-dialog-enter-active .p-dialog-leave-active Drawer .p-drawer-enter-active .p-drawer-leave-active Fieldset .p-collapsible-enter-active .p-collapsible-leave-active Galleria .p-galleria-enter-active .p-galleria-leave-active Image .p-image-original-enter-active .p-image-original-leave-active Menu .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active Message .p-message-enter-active .p-message-leave-active Modal Masks .p-overlay-mask-enter-active .p-overlay-mask-leave-active MultiSelect .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active Panel .p-collapsible-enter-active .p-collapsible-leave-active PanelMenu .p-collapsible-enter-active .p-collapsible-leave-active Password .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active Select .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active Stepper .p-collapsible-enter-active .p-collapsible-leave-active TieredMenu .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active Toast .p-toast-message-enter-active .p-toast-message-leave-active TreeSelect .p-anchored-overlay-enter-active .p-anchored-overlay-leave-active",
44405
+ "description": "List of class names of the CSS animations used by the components.\n\nComponent\nEnter Class\nLeave Class\n`Accordion`\n.p-collapsible-enter-active\n.p-collapsible-leave-active\n`AutoComplete`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`CascadeSelect`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`ColorPicker`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`ConfirmPopup`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`ContextMenu`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`DatePicker`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`Dialog`\n.p-dialog-enter-active\n.p-dialog-leave-active\n`Drawer`\n.p-drawer-enter-active\n.p-drawer-leave-active\n`Fieldset`\n.p-collapsible-enter-active\n.p-collapsible-leave-active\n`Galleria`\n.p-galleria-enter-active\n.p-galleria-leave-active\n`Image`\n.p-image-original-enter-active\n.p-image-original-leave-active\n`Menu`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`Message`\n.p-message-enter-active\n.p-message-leave-active\n`Modal Masks`\n.p-overlay-mask-enter-active\n.p-overlay-mask-leave-active\n`MultiSelect`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`Panel`\n.p-collapsible-enter-active\n.p-collapsible-leave-active\n`PanelMenu`\n.p-collapsible-enter-active\n.p-collapsible-leave-active\n`Password`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`Select`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`Stepper`\n.p-collapsible-enter-active\n.p-collapsible-leave-active\n`TieredMenu`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active\n`Toast`\n.p-toast-message-enter-active\n.p-toast-message-leave-active\n`TreeSelect`\n.p-anchored-overlay-enter-active\n.p-anchored-overlay-leave-active",
44420
44406
  "examples": null
44421
44407
  }
44422
44408
  ]
@@ -44430,7 +44416,7 @@
44430
44416
  {
44431
44417
  "id": "configuration",
44432
44418
  "label": "Configuration",
44433
- "description": "The ExhaustiveUI components natively support Right-to-Left (RTL) text direction through a modern CSS implementation utilizing FlexBox and classes like *-inline-start and *-block-end . Consequently, no JavaScript configuration is necessary; setting the document's text direction to RTL is sufficient to enable this feature. The RTL setting can either be set using the dir attribute or with the direction style property.",
44419
+ "description": "The ExhaustiveUI components natively support Right-to-Left (RTL) text direction through a modern CSS implementation utilizing FlexBox and classes like `*-inline-start` and `*-block-end`. Consequently, no JavaScript\nconfiguration is necessary; setting the document's text direction to RTL is sufficient to enable this feature.\n\nThe RTL setting can either be set using the `dir` attribute or with the `direction` style property.",
44434
44420
  "examples": null
44435
44421
  },
44436
44422
  {
@@ -44450,25 +44436,25 @@
44450
44436
  {
44451
44437
  "id": "compatibility",
44452
44438
  "label": "Compatibility",
44453
- "description": "If you are staying on PrimeFlex for now, ExhaustiveUI pairs with PrimeFlex v4 — the same combination that worked with PrimeNG v18 and newer, since the styling architecture is unchanged. PrimeFlex v3 targeted the older PrimeNG releases and is not a supported pairing here. Neither version is tested against ExhaustiveUI releases, so treat this as \"should work\", not as a supported configuration. The migration below is the path we actually maintain.",
44439
+ "description": "If you are staying on PrimeFlex for now, ExhaustiveUI pairs with PrimeFlex v4 — the same combination that worked with PrimeNG v18 and newer, since the styling architecture is unchanged. PrimeFlex v3 targeted the older PrimeNG releases\nand is not a supported pairing here.\n\nNeither version is tested against ExhaustiveUI releases, so treat this as \"should work\", not as a supported configuration. The migration below is the path we actually maintain.",
44454
44440
  "examples": null
44455
44441
  },
44456
44442
  {
44457
44443
  "id": "migration",
44458
44444
  "label": "Migration",
44459
- "description": "PrimeFlex class names map closely onto Tailwind's, so most of the work is mechanical. PrimeTek's primeclt ships a pf2tw command that does the conversion, and it works on any codebase — it rewrites class names and does not care which component library you use. Run pf2tw in a directory containing the files to convert. pf2tw was written for Tailwind v3. Tailwind v4 renamed a few of the utilities it produces, for example shadow-sm to shadow-xs , rounded to rounded-sm and flex-grow to grow . On Tailwind v4, check the converted classes against the renamed utilities list of the Tailwind upgrade guide. A handful of PrimeFlex classes have no Tailwind counterpart and are left alone. Replace them with flexbox or grid utilities by hand: formgrid formgroup formgroup-inline col col-fixed field field-checkbox field-radiobutton reset",
44445
+ "description": "PrimeFlex class names map closely onto Tailwind's, so most of the work is mechanical. PrimeTek's\n[primeclt](https://www.npmjs.com/package/primeclt) ships a `pf2tw` command that does the conversion, and it works on any codebase — it rewrites class names and does not care\nwhich component library you use.\n\n```bash\nnpm install -g primeclt\n```\n\nRun `pf2tw` in a directory containing the files to convert.\n\n```bash\nprime pf2tw\n```\n\n`pf2tw` was written for Tailwind v3. Tailwind v4 renamed a few of the utilities it produces, for example `shadow-sm` to `shadow-xs`, `rounded` to `rounded-sm` and `flex-grow` to `grow`. On Tailwind\nv4, check the converted classes against the [renamed utilities](https://tailwindcss.com/docs/upgrade-guide#renamed-utilities) list of the Tailwind upgrade guide.\n\nA handful of PrimeFlex classes have no Tailwind counterpart and are left alone. Replace them with flexbox or grid utilities by hand:\n\n- formgrid\n- formgroup\n- formgroup-inline\n- col\n- col-fixed\n- field\n- field-checkbox\n- field-radiobutton\n- reset",
44460
44446
  "examples": null
44461
44447
  },
44462
44448
  {
44463
44449
  "id": "overview",
44464
44450
  "label": "Overview",
44465
- "description": "PrimeFlex was PrimeTek's lightweight CSS utility library, designed to accompany PrimeNG. PrimeTek stopped maintaining it before the relicensing, on the grounds that most applications already bring their own utility layer — Tailwind, Bootstrap or something in-house — and a second one only overlaps with it. ExhaustiveUI does not maintain PrimeFlex either, and for the same reason. Nothing in this library depends on it, and no component requires it. If your application already uses PrimeFlex it will keep working, but it will not receive updates from us, and we suggest moving to Tailwind CSS.",
44451
+ "description": "[PrimeFlex](https://primeflex.org) was PrimeTek's lightweight CSS utility library, designed to accompany PrimeNG. PrimeTek stopped maintaining it before the relicensing, on the\ngrounds that most applications already bring their own utility layer — Tailwind, Bootstrap or something in-house — and a second one only overlaps with it.\n\nExhaustiveUI does not maintain PrimeFlex either, and for the same reason. Nothing in this library depends on it, and no component requires it. If your application already uses PrimeFlex it will keep working, but it will not receive\nupdates from us, and we suggest moving to Tailwind CSS.",
44466
44452
  "examples": null
44467
44453
  },
44468
44454
  {
44469
44455
  "id": "tailwindcss",
44470
44456
  "label": "Tailwindcss",
44471
- "description": "Tailwind CSS is the replacement we suggest. This documentation site is itself built with it, and we publish @exhaustive-ui/tailwindcss for first-class integration — a plugin that teaches Tailwind about the theme's design tokens and puts the component styles in a cascade layer you can override cleanly. See the Tailwind CSS guide for setup with either Tailwind v3 or v4, and the next section for converting existing PrimeFlex classes.",
44457
+ "description": "Tailwind CSS is the replacement we suggest. This documentation site is itself built with it, and we publish `@exhaustive-ui/tailwindcss` for first-class integration — a plugin that teaches Tailwind about the theme's design\ntokens and puts the component styles in a cascade layer you can override cleanly.\n\nSee the [Tailwind CSS guide](https://exhaustive-ui.com/tailwind) for setup with either Tailwind v3 or v4, and the next section for converting existing PrimeFlex classes.",
44472
44458
  "examples": null
44473
44459
  }
44474
44460
  ]
@@ -44480,39 +44466,39 @@
44480
44466
  "description": "Why ExhaustiveUI exists, what it commits to, and where it stops.",
44481
44467
  "sections": [
44482
44468
  {
44483
- "id": "governance",
44484
- "label": "Governance",
44485
- "description": "Everything happens in the open, in the repository . There is no private roadmap and no internal issue tracker. What you see in the issues, the discussions and the roadmap is the whole plan. Contributors earn commit access by contributing — the contribution guide describes the Contributor and Committer roles and roughly what it takes to reach them. We would rather grow the number of people who can merge a fix than route everything through one person. Breaking changes are avoided within a major and documented when a major requires them. Where we inherited a name that no longer fits — the CSS cascade layer, the package scope, the icon library — we changed it once, at v1, with a migration schematic, rather than dripping renames across releases.",
44469
+ "id": "origin",
44470
+ "label": "Why This Fork Exists",
44471
+ "description": "In June 2026 PrimeTek archived the PrimeNG repository and moved future major versions, starting with v22, to a commercial license. They explained their reasoning in\n[their own announcement](https://primeui.dev/nextchapter), and it is worth reading. Maintaining a component library of this size for a decade, largely for free, is genuinely hard,\nand we do not think the decision was made lightly.\n\nIt did, however, leave a lot of applications on a library with no further open source releases. ExhaustiveUI exists for those applications. It is a community fork of the last MIT licensed version of PrimeNG, v21, and it stays MIT.\n\nThis is not an official fork and it is not endorsed by PrimeTek. It is a separate repository, seeded with PrimeNG's code and history, maintained by people who depend on it.",
44486
44472
  "examples": null
44487
44473
  },
44488
44474
  {
44489
- "id": "limits",
44490
- "label": "Limits",
44491
- "description": "Naming the limits is what makes the commitments above worth anything. Here is what ExhaustiveUI is not. There is no commercial support No SLA, no support contract, no guaranteed response time. Issues and discussions are answered by volunteers when they have time. If your organisation needs contractual guarantees, this project cannot provide them and you should plan accordingly. There are no premium templates, blocks or design tooling PrimeTek's application templates, block library and visual theme designer are their commercial products. They are not part of what was MIT licensed, so they are not part of this fork and will not be reimplemented. Theming here means editing preset objects in code, which is documented in full. We are not chasing feature parity with PrimeNG v22 and beyond PrimeNG continues under its own license and its own roadmap. ExhaustiveUI diverges from v21 forward. Some things they add, we will not have. Some things we fix, they will not. Treat the two as separate libraries that share an ancestor, not as a free copy of a paid product. The bus factor is real This is maintained by a small group of people in their own time. We would rather say that plainly than imply a larger organisation stands behind it. The best way to change that number is to contribute .",
44475
+ "id": "promises",
44476
+ "label": "What We Commit To",
44477
+ "description": "Four commitments, in the order we would want to read them if we were choosing a dependency:\n\n### MIT, with no second tier\n\nEvery package we publish is MIT licensed. There is no paid edition, no enterprise build, no feature held back behind a subscription, and no plan to introduce one. If that ever changed, it would be a fork of this project rather than a\nrelicensing of it, because the code we inherited is MIT and so is everything we add to it.\n\n### We track Angular\n\nOur release cadence follows Angular's. When a new Angular major lands, the priority is a compatible ExhaustiveUI major — before new features, before refactors. Staying upgradeable is the single most valuable thing a component library\ncan do for the applications built on it.\n\n### Bugs before features\n\nWe inherited a large backlog along with the code. Fixing what is broken ranks above adding what is missing. Feature requests are triaged and welcome, but they generally ship when someone in the community implements them.\n\n### No surprises in your bundle\n\nThe library sends no telemetry, phones no home, and requires no account or key to use. What you install is what runs.",
44492
44478
  "examples": null
44493
44479
  },
44494
44480
  {
44495
- "id": "origin",
44496
- "label": "Origin",
44497
- "description": "In June 2026 PrimeTek archived the PrimeNG repository and moved future major versions, starting with v22, to a commercial license. They explained their reasoning in their own announcement , and it is worth reading. Maintaining a component library of this size for a decade, largely for free, is genuinely hard, and we do not think the decision was made lightly. It did, however, leave a lot of applications on a library with no further open source releases. ExhaustiveUI exists for those applications. It is a community fork of the last MIT licensed version of PrimeNG, v21, and it stays MIT. This is not an official fork and it is not endorsed by PrimeTek. It is a separate repository, seeded with PrimeNG's code and history, maintained by people who depend on it.",
44481
+ "id": "limits",
44482
+ "label": "What We Do Not Do",
44483
+ "description": "Naming the limits is what makes the commitments above worth anything. Here is what ExhaustiveUI is not.\n\n### There is no commercial support\n\nNo SLA, no support contract, no guaranteed response time. Issues and discussions are answered by volunteers when they have time. If your organisation needs contractual guarantees, this project cannot provide them and you should plan\naccordingly.\n\n### There are no premium templates, blocks or design tooling\n\nPrimeTek's application templates, block library and visual theme designer are their commercial products. They are not part of what was MIT licensed, so they are not part of this fork and will not be reimplemented. Theming here means\nediting preset objects in code, which is documented in full.\n\n### We are not chasing feature parity with PrimeNG v22 and beyond\n\nPrimeNG continues under its own license and its own roadmap. ExhaustiveUI diverges from v21 forward. Some things they add, we will not have. Some things we fix, they will not. Treat the two as separate libraries that share an\nancestor, not as a free copy of a paid product.\n\n### The bus factor is real\n\nThis is maintained by a small group of people in their own time. We would rather say that plainly than imply a larger organisation stands behind it. The best way to change that number is to\n[contribute](https://github.com/e-xiste/exhaustive-ui).",
44498
44484
  "examples": null
44499
44485
  },
44500
44486
  {
44501
- "id": "promises",
44502
- "label": "Promises",
44503
- "description": "Four commitments, in the order we would want to read them if we were choosing a dependency: MIT, with no second tier Every package we publish is MIT licensed. There is no paid edition, no enterprise build, no feature held back behind a subscription, and no plan to introduce one. If that ever changed, it would be a fork of this project rather than a relicensing of it, because the code we inherited is MIT and so is everything we add to it. We track Angular Our release cadence follows Angular's. When a new Angular major lands, the priority is a compatible ExhaustiveUI major — before new features, before refactors. Staying upgradeable is the single most valuable thing a component library can do for the applications built on it. Bugs before features We inherited a large backlog along with the code. Fixing what is broken ranks above adding what is missing. Feature requests are triaged and welcome, but they generally ship when someone in the community implements them. No surprises in your bundle The library sends no telemetry, phones no home, and requires no account or key to use. What you install is what runs.",
44487
+ "id": "governance",
44488
+ "label": "How Decisions Are Made",
44489
+ "description": "Everything happens in the open, in the [repository](https://github.com/e-xiste/exhaustive-ui). There is no private roadmap and no internal issue tracker. What you see in the issues,\nthe discussions and the [roadmap](https://exhaustive-ui.com/roadmap) is the whole plan.\n\nContributors earn commit access by contributing — the [contribution guide](https://exhaustive-ui.com/contribution) describes the Contributor and Committer roles and roughly what it takes to reach them. We would rather\ngrow the number of people who can merge a fix than route everything through one person.\n\nBreaking changes are avoided within a major and documented when a major requires them. Where we inherited a name that no longer fits — the CSS cascade layer, the package scope, the icon library — we changed it once, at v1, with a\nmigration schematic, rather than dripping renames across releases.",
44504
44490
  "examples": null
44505
44491
  },
44506
44492
  {
44507
- "id": "sustainability",
44508
- "label": "Sustainability",
44509
- "description": "The honest answer to \"how is this funded\" is: it mostly is not. e-xiste covers the hosting and the domain; the work is volunteered. That is a fragile arrangement, and it is the main risk to this project — larger than any technical risk we can see today. The things that actually help, roughly in order of impact: Reproducing and triaging issues. A bug with a minimal reproduction is several times more likely to get fixed. Sending pull requests, especially for issues labelled help-needed . Answering questions in discussions, so the same answer is not written five times. Improving this documentation. Every page has a source file and every fix is welcome. Telling your employer you depend on it. Sponsored maintenance time is worth more than any one-off donation. The contribution guide covers how to get started.",
44493
+ "id": "trademark",
44494
+ "label": "PrimeNG and PrimeTek",
44495
+ "description": "ExhaustiveUI is not affiliated with, endorsed by, or sponsored by PrimeTek. PrimeNG, PrimeFaces, PrimeReact, PrimeVue and PrimeFlex are their trademarks. The rename from the inherited names — the packages, the CSS layer, the icon\nlibrary — is a trademark matter, not a technical one, and it is why we ship a [migration schematic](https://exhaustive-ui.com/migration/primeng) rather than asking you to rewrite imports by hand.\n\nReferences to PrimeNG remain throughout this documentation and the source, and they are deliberate. Attribution is the point: this library is PrimeTek's decade of work plus whatever the community adds on top. Pretending otherwise\nwould be both dishonest and useless to anyone trying to find their way around a familiar API.\n\nThe code we forked was published under the MIT license, and we distribute it under those same terms, with the original copyright notices intact.",
44510
44496
  "examples": null
44511
44497
  },
44512
44498
  {
44513
- "id": "trademark",
44514
- "label": "Trademark",
44515
- "description": "ExhaustiveUI is not affiliated with, endorsed by, or sponsored by PrimeTek. PrimeNG, PrimeFaces, PrimeReact, PrimeVue and PrimeFlex are their trademarks. The rename from the inherited names — the packages, the CSS layer, the icon library — is a trademark matter, not a technical one, and it is why we ship a migration schematic rather than asking you to rewrite imports by hand. References to PrimeNG remain throughout this documentation and the source, and they are deliberate. Attribution is the point: this library is PrimeTek's decade of work plus whatever the community adds on top. Pretending otherwise would be both dishonest and useless to anyone trying to find their way around a familiar API. The code we forked was published under the MIT license, and we distribute it under those same terms, with the original copyright notices intact.",
44499
+ "id": "sustainability",
44500
+ "label": "Sustainability",
44501
+ "description": "The honest answer to \"how is this funded\" is: it mostly is not. e-xiste covers the hosting and the domain; the work is volunteered. That is a fragile arrangement, and it is the main risk to this project — larger than any technical\nrisk we can see today.\n\nThe things that actually help, roughly in order of impact:\n\n- Reproducing and triaging issues. A bug with a minimal reproduction is several times more likely to get fixed.\n- Sending pull requests, especially for issues labelled `help-needed`.\n- Answering questions in discussions, so the same answer is not written five times.\n- Improving this documentation. Every page has a source file and every fix is welcome.\n- Telling your employer you depend on it. Sponsored maintenance time is worth more than any one-off donation.\n\nThe [contribution guide](https://exhaustive-ui.com/contribution) covers how to get started.",
44516
44502
  "examples": null
44517
44503
  }
44518
44504
  ]
@@ -44524,27 +44510,27 @@
44524
44510
  "description": "Licensing, migration from PrimeNG, the ecosystem, and how support works.",
44525
44511
  "sections": [
44526
44512
  {
44527
- "id": "ecosystem",
44528
- "label": "Ecosystem",
44529
- "description": "Do the PrimeNG themes work? The built-in presets do — Aura, Material, Lara and Nora ship in @exhaustive-ui/themes and are configured the same way. A preset you wrote yourself against PrimeNG v21 will work after the import paths are updated, which the migration schematic handles. What about the Theme Designer, templates and blocks? Those are PrimeTek's commercial products. They were never MIT licensed, so they are not part of this fork and we will not be reimplementing them. Theming in ExhaustiveUI means editing preset objects in code, which is documented in full under styled mode . What replaced PrimeIcons? OpenNG Icons , installed as @openng/icons . The pi pi-{icon} class names are unchanged, so templates do not need editing — only the package name and the stylesheet import, both of which the migration schematic rewrites. What about PrimeFlex? PrimeFlex is not maintained here. We suggest Tailwind CSS instead, and ship @exhaustive-ui/tailwindcss for first-class integration — see the Tailwind guide . The PrimeFlex guide covers moving across. Does ExhaustiveUI work with SSR? This documentation site is itself an Angular SSR application built on ExhaustiveUI, prerendered at build time. So yes, and any regression there tends to be noticed quickly.",
44513
+ "id": "project",
44514
+ "label": "The Project",
44515
+ "description": "### Is ExhaustiveUI free? Will it stay free?\n\nYes, and yes. Every package is MIT licensed, and the code we forked was MIT too, so relicensing it is not something we could do even if we wanted to. There is no paid tier and none is planned. The\n[philosophy page](https://exhaustive-ui.com/philosophy) goes into what that does and does not buy you.\n\n### Is this an official PrimeNG fork? Are you affiliated with PrimeTek?\n\nNo. ExhaustiveUI is an independent community fork, not affiliated with, endorsed by, or sponsored by PrimeTek. It is a fork of\n[Optimus UI](https://github.com/openng-org/optimus-ui) (OpenNG), itself a repository seeded with PrimeNG's MIT licensed code and history, not a fork of the archived\n`primefaces/primeng` repository.\n\n### Which PrimeNG version is this forked from?\n\nPrimeNG v21, the last version published under the MIT license, by way of Optimus UI v2. ExhaustiveUI v22 is that codebase, rebranded and migrated to the Angular Signals API, with the fixes that have landed since; its major version\nnumber follows Angular's.\n\n### Who maintains it, and how is it funded?\n\nA small group of volunteers, with e-xiste covering hosting and the domain. We are deliberate about not implying more than that — see\n[sustainability](https://exhaustive-ui.com/philosophy) for the honest version and the ways that can change.\n\n### Why did the name change?\n\nTrademark, twice over. PrimeNG, PrimeFaces and PrimeFlex are PrimeTek's marks, and Optimus UI is OpenNG's, so the packages and the CSS cascade layer needed a name of their own. That is also why the rename from PrimeNG is handled by a\nschematic rather than by asking you to rewrite imports by hand.",
44530
44516
  "examples": null
44531
44517
  },
44532
44518
  {
44533
44519
  "id": "migration",
44534
- "label": "Migration",
44535
- "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.",
44520
+ "label": "Compatibility & Migration",
44521
+ "description": "### Which Angular versions are supported?\n\nAngular 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\n[version compatibility table](https://exhaustive-ui.com/migration/update) in the update guide.\n\n### How do I migrate from PrimeNG? Is it automatic?\n\nMostly, 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\n`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,\nwith file and line numbers. The [migration guide](https://exhaustive-ui.com/migration/primeng) covers the details and the manual cases.\n\n### I am on PrimeNG v20 or older. Can I migrate directly?\n\nNo. 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.\n\n### I use Optimus UI. Can I switch?\n\nYes. ExhaustiveUI is a fork of Optimus UI, with the same components. On Optimus UI v2, run `ng generate @exhaustive-ui/core:migrate-from-optimus`: packages swapped, imports and configuration API renamed, CSS layer renamed,\ndependencies installed. The [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) covers the steps and the v22 migrations that follow.\n\n### What happens to my PrimeNG license?\n\nNothing — 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\nover here.\n\n### I had an open PR on primefaces/primeng. Can I bring it here?\n\nYes, 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\ncleanly.\n\n### Can I run PrimeNG and ExhaustiveUI side by side?\n\nTechnically 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\nconfiguration.",
44536
44522
  "examples": null
44537
44523
  },
44538
44524
  {
44539
- "id": "project",
44540
- "label": "Project",
44541
- "description": "Is ExhaustiveUI free? Will it stay free? Yes, and yes. Every package is MIT licensed, and the code we forked was MIT too, so relicensing it is not something we could do even if we wanted to. There is no paid tier and none is planned. The philosophy page goes into what that does and does not buy you. Is this an official PrimeNG fork? Are you affiliated with PrimeTek? No. ExhaustiveUI is an independent community fork, not affiliated with, endorsed by, or sponsored by PrimeTek. It is a fork of Optimus UI (OpenNG), itself a repository seeded with PrimeNG's MIT licensed code and history, not a fork of the archived primefaces/primeng repository. Which PrimeNG version is this forked from? PrimeNG v21, the last version published under the MIT license, by way of Optimus UI v2. ExhaustiveUI v22 is that codebase, rebranded and migrated to the Angular Signals API, with the fixes that have landed since; its major version number follows Angular's. Who maintains it, and how is it funded? A small group of volunteers, with e-xiste covering hosting and the domain. We are deliberate about not implying more than that — see sustainability for the honest version and the ways that can change. Why did the name change? Trademark, twice over. PrimeNG, PrimeFaces and PrimeFlex are PrimeTek's marks, and Optimus UI is OpenNG's, so the packages and the CSS cascade layer needed a name of their own. That is also why the rename from PrimeNG is handled by a schematic rather than by asking you to rewrite imports by hand.",
44525
+ "id": "ecosystem",
44526
+ "label": "Themes, Icons & Ecosystem",
44527
+ "description": "### Do the PrimeNG themes work?\n\nThe built-in presets do — Aura, Material, Lara and Nora ship in `@exhaustive-ui/themes` and are configured the same way. A preset you wrote yourself against PrimeNG v21 will work after the import paths are updated, which the\nmigration schematic handles.\n\n### What about the Theme Designer, templates and blocks?\n\nThose are PrimeTek's commercial products. They were never MIT licensed, so they are not part of this fork and we will not be reimplementing them. Theming in ExhaustiveUI means editing preset objects in code, which is documented in\nfull under [styled mode](https://exhaustive-ui.com/theming/styled).\n\n### What replaced PrimeIcons?\n\n[OpenNG Icons](https://exhaustive-ui.com/icons), installed as `@openng/icons`. The `pi pi-{icon}` class names are unchanged, so templates do not need editing — only the package name and the\nstylesheet import, both of which the migration schematic rewrites.\n\n### What about PrimeFlex?\n\nPrimeFlex is not maintained here. We suggest Tailwind CSS instead, and ship `@exhaustive-ui/tailwindcss` for first-class integration — see the [Tailwind guide](https://exhaustive-ui.com/tailwind). The\n[PrimeFlex guide](https://exhaustive-ui.com/guides/primeflex) covers moving across.\n\n### Does ExhaustiveUI work with SSR?\n\nThis documentation site is itself an Angular SSR application built on ExhaustiveUI, prerendered at build time. So yes, and any regression there tends to be noticed quickly.",
44542
44528
  "examples": null
44543
44529
  },
44544
44530
  {
44545
44531
  "id": "support",
44546
- "label": "Support",
44547
- "description": "Is there commercial support? No. There is no SLA, no support contract and no guaranteed response time. Issues and discussions are answered by volunteers when they have time. If your organisation needs contractual guarantees, this project cannot offer them. How do I report a bug? Open an issue on GitHub with a minimal reproduction — a StackBlitz from any demo on this site is ideal — plus your ExhaustiveUI, Angular and browser versions. A reproduction is the difference between a bug that gets fixed and one that sits in the backlog. How do I request a feature? Open a discussion . Requests are triaged and welcome, but in practice they ship when someone implements them. If it matters to you, the contribution guide is the fastest route. Where do I ask questions? GitHub Discussions is the primary place. There is no chat server; a written question with a reproduction gets a better answer than a real-time one. How does versioning work? Semantic versioning, with majors tracking Angular majors. Breaking changes are confined to majors and documented in the GitHub releases .",
44532
+ "label": "Support & Contributing",
44533
+ "description": "### Is there commercial support?\n\nNo. There is no SLA, no support contract and no guaranteed response time. Issues and discussions are answered by volunteers when they have time. If your organisation needs contractual guarantees, this project cannot offer them.\n\n### How do I report a bug?\n\nOpen an issue on [GitHub](https://github.com/e-xiste/exhaustive-ui/issues) with a minimal reproduction — a StackBlitz from any demo on this site is ideal — plus your ExhaustiveUI,\nAngular and browser versions. A reproduction is the difference between a bug that gets fixed and one that sits in the backlog.\n\n### How do I request a feature?\n\nOpen a [discussion](https://github.com/e-xiste/exhaustive-ui/discussions). Requests are triaged and welcome, but in practice they ship when someone implements them. If it matters to\nyou, the [contribution guide](https://exhaustive-ui.com/contribution) is the fastest route.\n\n### Where do I ask questions?\n\nGitHub Discussions is the primary place. There is no chat server; a written question with a reproduction gets a better answer than a real-time one.\n\n### How does versioning work?\n\nSemantic versioning, with majors tracking Angular majors. Breaking changes are confined to majors and documented in the\n[GitHub releases](https://github.com/e-xiste/exhaustive-ui/releases).",
44548
44534
  "examples": null
44549
44535
  }
44550
44536
  ]
@@ -44553,41 +44539,211 @@
44553
44539
  "name": "update",
44554
44540
  "path": "migration/update",
44555
44541
  "title": "Update ExhaustiveUI",
44556
- "description": "Updating with ng update, Angular version compatibility, and what changes in v22 (Signals API, OnPush, automated migrations).",
44542
+ "description": "Updating with ng update, Angular version compatibility, and a summary of what changes in v22.",
44557
44543
  "sections": [
44558
44544
  {
44559
- "id": "major-versions",
44560
- "label": "Major-versions",
44561
- "description": "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.",
44562
- "examples": {
44563
- "command": "ng update @angular/core@23 @angular/cli@23\nng update @exhaustive-ui/core@23"
44564
- }
44545
+ "id": "overview",
44546
+ "label": "Overview",
44547
+ "description": "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\nnew 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.\n\nMajor 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.\n\nThis page is about updating a project that already uses ExhaustiveUI. To move an existing workspace across, see the guides for\n[PrimeNG](https://exhaustive-ui.com/migration/primeng) and [Optimus UI](https://exhaustive-ui.com/migration/optimus) instead.",
44548
+ "examples": null
44549
+ },
44550
+ {
44551
+ "id": "updating",
44552
+ "label": "Updating",
44553
+ "description": "Run `ng update` without arguments at any time to list the updates available in your workspace, ExhaustiveUI included.\n\n```bash\nng update\n```\n\nTo 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 —\nthemes, locale, Tailwind CSS plugin and the internal runtime packages — is updated together and the suite cannot end up on mixed versions.\n\n```bash\nng update @exhaustive-ui/core\n```\n\nLike 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.",
44554
+ "examples": null
44565
44555
  },
44566
44556
  {
44567
- "id": "ng-update",
44568
- "label": "Ng-update",
44569
- "description": "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.",
44557
+ "id": "angular-compatibility",
44558
+ "label": "Angular Version Compatibility",
44559
+ "description": "Each ExhaustiveUI major targets a single Angular major.\n\nTo 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\npassing the target version. For example, once Angular v23 and ExhaustiveUI v23 are out, from v22:\n\n```bash\nng update @angular/core@23 @angular/cli@23\nng update @exhaustive-ui/core@23\n```\n\nReview the release notes of the target version for breaking changes before you start.",
44570
44560
  "examples": null
44571
44561
  },
44562
+ {
44563
+ "id": "v22",
44564
+ "label": "Updating to v22",
44565
+ "description": "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\nwrites 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.\n\n```bash\nng update @angular/core@22 @angular/cli@22\nng update @exhaustive-ui/core@22\n```\n\nThe [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\nand type changes.",
44566
+ "examples": null
44567
+ },
44568
+ {
44569
+ "id": "release-notes",
44570
+ "label": "Release Notes",
44571
+ "description": "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\nmanual steps a release requires. Check the notes for the target version before a major update.",
44572
+ "examples": null
44573
+ }
44574
+ ]
44575
+ },
44576
+ {
44577
+ "name": "primeng",
44578
+ "path": "migration/primeng",
44579
+ "title": "Migrating from PrimeNG",
44580
+ "description": "Moving a PrimeNG v21 application to ExhaustiveUI: the migrate-from-primeng schematic, what it changes (packages, imports, configuration API, icons, CSS layer), the manual checks and the v22 migrations.",
44581
+ "sections": [
44572
44582
  {
44573
44583
  "id": "overview",
44574
44584
  "label": "Overview",
44575
- "description": "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.",
44585
+ "description": "ExhaustiveUI is an MIT fork of PrimeNG v21, the last PrimeNG release published under the MIT license, by way of Optimus UI. The components, their selectors, the `p-*` CSS classes, the design tokens and the `pi pi-*` icon\nclasses are the same, so a PrimeNG v21 application moves across in two parts:\n\n1. **The switch**: other package names, a configuration API named after ExhaustiveUI, another icon package and another default CSS layer name. The `migrate-from-primeng` schematic does it.\n2. **The v22 changes**: Angular 22, the Signals API, OnPush and the API cleanup of ExhaustiveUI v22. The `ng update` migrations do most of it, and the [migration guide to v22](https://exhaustive-ui.com/migration/v22) covers the rest.\n\nNo license is needed. A PrimeTek license or subscription for PrimeNG, its templates or its theme designer does not carry over, and is not required.",
44576
44586
  "examples": null
44577
44587
  },
44578
44588
  {
44579
- "id": "release-notes",
44580
- "label": "Release-notes",
44581
- "description": "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.",
44589
+ "id": "prerequisites",
44590
+ "label": "Before you start",
44591
+ "description": "- **PrimeNG v21.** ExhaustiveUI shares its API. On v20 or older, upgrade to v21 first with PrimeNG's own update guides; the schematic checks the installed version and stops otherwise. On PrimeNG v22, the schematic runs, but the features PrimeNG added after v21 have no ExhaustiveUI equivalent: check the compiler errors and the report.\n- **A clean git working tree**, so every change can be reviewed and reverted on its own, and a build and test run that passes before you start.\n- **PrimeFlex**, if the project uses it, is not migrated by this schematic. Run `migrate-from-primeflex` afterwards to move its classes to Tailwind CSS; the schematic reminds you when it finds PrimeFlex.",
44592
+ "examples": null
44593
+ },
44594
+ {
44595
+ "id": "steps",
44596
+ "label": "Migration steps",
44597
+ "description": "1. Update Angular to 22. PrimeNG v21 declares Angular 21 as its peer dependency, so the Angular CLI refuses the update while `primeng` is installed: pass `--force`. The next step removes `primeng`.\n2. Install ExhaustiveUI and run the `migrate-from-primeng` schematic. It rewrites the workspace, then installs the new dependencies.\n3. Run the v22 migrations. The workspace did not go through `ng update`, so they are run explicitly, from the version before v22.\n4. Read both reports, fix the compiler errors, then build and run your tests.\n\n```bash\nng update @angular/core@22 @angular/cli@22 --force\nnpm install @exhaustive-ui/core@22\nng generate @exhaustive-ui/core:migrate-from-primeng\nng update @exhaustive-ui/core --migrate-only --from=3.0.0\n```\n\nThe schematic takes two options: `--skip-install` leaves the install to you, and `--force` skips the PrimeNG version check.",
44598
+ "examples": null
44599
+ },
44600
+ {
44601
+ "id": "schematic",
44602
+ "label": "What the schematic changes",
44603
+ "description": "The schematic visits every file of the workspace except `node_modules`, build output and the files your `.gitignore` excludes.\n\n### Dependencies\n\nIn every `package.json` of the workspace, including `overrides` and `resolutions`, each package is replaced by its counterpart:\n\n- `primeng` becomes `@exhaustive-ui/core`\n- `@primeuix/themes`, `@primeuix/styled`, `@primeuix/styles`, `@primeuix/utils` and `@primeuix/motion` become `@exhaustive-ui/themes`, `@exhaustive-ui/styled`, `@exhaustive-ui/styles`, `@exhaustive-ui/utils` and `@exhaustive-ui/motion`\n- `tailwindcss-primeui` becomes `@exhaustive-ui/tailwindcss`\n- `primelocale` becomes `@exhaustive-ui/locale`\n- `primeicons` becomes `@openng/icons`\n\n### TypeScript\n\nImports, dynamic imports and `require()` calls are rewritten, subpaths included (`primeng/button` becomes `@exhaustive-ui/core/button`, `@primeuix/themes/aura` becomes\n`@exhaustive-ui/themes/aura`), and so is the Tailwind CSS configuration file. The configuration API is renamed where it is imported: `providePrimeNG` becomes `provideExhaustive`, the `PrimeNG` service becomes\n`Exhaustive`, `PrimeNGConfigType` becomes `ExhaustiveConfigType`, and the `PrimeIcons` constants become `OpenngIcons`.\n\n```typescript\n// Before\nimport { ApplicationConfig } from '@angular/core';\nimport { providePrimeNG } from 'primeng/config';\nimport Aura from '@primeuix/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [providePrimeNG({ theme: { preset: Aura } })]\n};\n\n// After\nimport { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [provideExhaustive({ theme: { preset: Aura } })]\n};\n```\n\n### Stylesheets and angular.json\n\n`@import`, `@use`, `@plugin` and `url()` references in stylesheets, and the `styles` and `scripts` entries of `angular.json` and `project.json`, follow the new package names.\n`primeicons/primeicons.css` becomes `@openng/icons/openng-icons.css`; the `pi pi-*` classes in templates do not change.\n\n### CSS cascade layer\n\nWhen the theme sets `cssLayer`, the `primeng` layer becomes `exhaustive` in its `name` and `order`, `primeng-overwrites` becomes `exhaustive-overwrites`, and the matching\n`@layer` declarations in your stylesheets are renamed too, so your overrides keep their place in the layer order. With `cssLayer: true`, the configuration does not change, and only the stylesheets are renamed.\n\n### The report\n\nThe schematic ends with the places that still mention `primeng`, `primeicons`, `@primeuix`, `tailwindcss-primeui` or `primelocale`, with the file and line: templates, Markdown, JSON or code it does not\nrewrite. Lockfiles are left out of the report, since the install regenerates them.",
44604
+ "examples": null
44605
+ },
44606
+ {
44607
+ "id": "manual",
44608
+ "label": "Manual checks",
44609
+ "description": "Besides the places listed in the report, check these by hand:\n\n- **The icon font name.** A stylesheet that names the font directly, as in `font-family: 'primeicons'`, now needs `'openng-icons'`. The schematic does not touch declaration values.\n- **Local variables named after PrimeNG**, such as `primeng = inject(PrimeNG)`: the type is renamed, the variable name is yours to keep or change.\n- **Module paths passed to other functions**, such as `jest.mock('primeng/button')` or `vi.mock()`: only imports, dynamic imports and `require()` are rewritten. These appear in the report.\n- **Build and deployment files** outside the TypeScript sources and stylesheets: Dockerfiles, CI scripts, CDN links to PrimeNG or PrimeIcons.\n- **PrimeTek products** such as templates or the theme designer are not part of ExhaustiveUI. A preset built with them is a plain `definePreset()` object and keeps working once its imports point to `@exhaustive-ui/themes`.",
44582
44610
  "examples": null
44583
44611
  },
44584
44612
  {
44585
44613
  "id": "v22",
44586
- "label": "V22",
44587
- "description": "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:",
44588
- "examples": {
44589
- "command": "ng update @angular/core@22 @angular/cli@22\nng update @exhaustive-ui/core@22"
44590
- }
44614
+ "label": "What changes in v22",
44615
+ "description": "After the switch, the application runs on ExhaustiveUI v22, which differs from PrimeNG v21 in ways the compiler and your tests will show. The [migration guide to v22](https://exhaustive-ui.com/migration/v22)\ndetails each of them:\n\n- Inputs, two-way properties, outputs and queries are signals: code holding a component instance reads inputs with a call and writes two-way properties with `.set()`.\n- Components use OnPush change detection, except Table, TreeTable and DynamicDialog: give them new arrays and objects, or signals, rather than mutating bound data.\n- Deprecated and inactive inputs are removed or renamed, `styleClass` becomes `class` on most components; the v22 migrations rewrite these bindings and report the rest.\n- Hundreds of bugs inherited from PrimeNG v21 are fixed, each with a regression test; a few of them change a visible behavior.",
44616
+ "examples": null
44617
+ },
44618
+ {
44619
+ "id": "checklist",
44620
+ "label": "Checklist",
44621
+ "description": "- Angular 22 installed, and no `primeng`, `@primeuix/*`, `primeicons`, `tailwindcss-primeui` or `primelocale` left in any `package.json`.\n- The report of `migrate-from-primeng` handled, then the report of the v22 migrations.\n- Icons render: the stylesheet is `@openng/icons/openng-icons.css` and nothing names the `primeicons` font.\n- With a CSS layer configured, your overrides still apply: the `@layer` names match the theme's `cssLayer` order.\n- The application compiles and its tests pass, after the code changes of the migration guide to v22.\n- PrimeFlex, if used, migrated with `migrate-from-primeflex`.",
44622
+ "examples": null
44623
+ }
44624
+ ]
44625
+ },
44626
+ {
44627
+ "name": "optimus",
44628
+ "path": "migration/optimus",
44629
+ "title": "Migrating from Optimus UI",
44630
+ "description": "Moving an Optimus UI v2 application to ExhaustiveUI: package and configuration API renames, the CSS layer name, then the v22 migrations.",
44631
+ "sections": [
44632
+ {
44633
+ "id": "overview",
44634
+ "label": "Overview",
44635
+ "description": "ExhaustiveUI is a fork of Optimus UI, itself the MIT continuation of PrimeNG v21. An Optimus UI v2 application already runs on Angular 22 and uses the same components, selectors, CSS classes, design tokens and\n`@openng/icons` icons. Moving it across takes two steps:\n\n1. **The rename**: the `@openng/optimus-ui*` packages become `@exhaustive-ui/*`, and the four names of the configuration API change. The `migrate-from-optimus` schematic does it.\n2. **The v22 changes**: the Signals API everywhere, OnPush and the API cleanup of ExhaustiveUI v22. The `ng update` migrations do most of it, and the [migration guide to v22](https://exhaustive-ui.com/migration/v22) covers the rest.",
44636
+ "examples": null
44637
+ },
44638
+ {
44639
+ "id": "prerequisites",
44640
+ "label": "Before you start",
44641
+ "description": "- **Optimus UI v2 on Angular 22.** An application still on Optimus UI v1 updates to v2 first, following Optimus UI's documentation.\n- **A clean git working tree**, so the rename and the migrations can be reviewed on their own, and a build and test run that passes before you start.",
44642
+ "examples": null
44643
+ },
44644
+ {
44645
+ "id": "steps",
44646
+ "label": "Migration steps",
44647
+ "description": "1. Install ExhaustiveUI and run the `migrate-from-optimus` schematic. It rewrites the workspace, then installs the new dependencies.\n2. Run the v22 migrations. The workspace did not go through `ng update`, so they are run explicitly, from the version before v22.\n3. Read both reports, fix the compiler errors, then build and run your tests.\n\n```bash\nnpm install @exhaustive-ui/core@22\nng generate @exhaustive-ui/core:migrate-from-optimus\nng update @exhaustive-ui/core --migrate-only --from=3.0.0\n```\n\nThe schematic checks that `@openng/optimus-ui` v2 is installed. It takes two options: `--skip-install` leaves the install to you, and `--force` skips the version check. Like `ng update`, run it on a clean\nworking tree so its changes can be reviewed with `git diff`.",
44648
+ "examples": null
44649
+ },
44650
+ {
44651
+ "id": "schematic",
44652
+ "label": "What the schematic changes",
44653
+ "description": "The schematic visits every file of the workspace except `node_modules`, build output and the files your `.gitignore` excludes.\n\n### Dependencies\n\nIn every `package.json` of the workspace, each package is replaced by its counterpart, which has the same content and the same subpaths:\n\n- `@openng/optimus-ui` becomes `@exhaustive-ui/core`\n- `@openng/optimus-ui-themes`, `-tailwindcss`, `-locale`, `-styled`, `-styles`, `-utils` and `-motion` become `@exhaustive-ui/themes`, `tailwindcss`, `locale`, `styled`, `styles`, `utils` and `motion`\n- `@openng/icons` stays: ExhaustiveUI uses the same icon set.\n\n### TypeScript\n\nImports, dynamic imports and `require()` calls are rewritten, subpaths included (`@openng/optimus-ui/button` becomes `@exhaustive-ui/core/button`), and so is the Tailwind CSS configuration file. The\nconfiguration API is renamed where it is imported from Optimus UI, along with every use in the file: `provideOptimus` becomes `provideExhaustive`, the `Optimus` service becomes `Exhaustive`,\n`OptimusConfigType` becomes `ExhaustiveConfigType` and `OPTIMUS_CONFIG` becomes `EXHAUSTIVE_CONFIG`. A class of your own that happens to be named `Optimus` is left alone.\n\n```typescript\n// Before\nimport { ApplicationConfig } from '@angular/core';\nimport { provideOptimus } from '@openng/optimus-ui/config';\nimport Aura from '@openng/optimus-ui-themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [provideOptimus({ theme: { preset: Aura } })]\n};\n\n// After\nimport { ApplicationConfig } from '@angular/core';\nimport { provideExhaustive } from '@exhaustive-ui/core/config';\nimport Aura from '@exhaustive-ui/themes/aura';\n\nexport const appConfig: ApplicationConfig = {\n providers: [provideExhaustive({ theme: { preset: Aura } })]\n};\n```\n\n### Stylesheets and angular.json\n\n`@import`, `@use`, `@plugin` and `url()` references in stylesheets, and the `styles` and `scripts` entries of `angular.json` and `project.json`, follow the new package names.\n\n### The report\n\nThe schematic ends with the places that still mention `optimus-ui`, `Optimus`, `provideOptimus`, `OptimusConfigType` or `OPTIMUS_CONFIG`, with the file and line: templates, Markdown, comments, or module paths\npassed to other functions, such as `jest.mock()`. Lockfiles are left out, since the install regenerates them.",
44654
+ "examples": null
44655
+ },
44656
+ {
44657
+ "id": "css-layer",
44658
+ "label": "CSS layer",
44659
+ "description": "Optimus UI puts its styles in a CSS cascade layer named `optimus` when the theme enables `cssLayer`; ExhaustiveUI names it `exhaustive`. The schematic renames the `optimus` token in the `cssLayer`\n`name` and `order` of your configuration, then the matching `@layer` declarations and `@import ... layer()` clauses in your stylesheets, so your overrides keep their place in the layer order. With\n`cssLayer: true`, the configuration does not change, and only the stylesheets are renamed.\n\nA layer of your own, with another name, is left as it is. The CSS classes (`p-button`...), the design tokens (`--p-primary-color`...) and the icon classes (`pi pi-check`...) do not change.",
44660
+ "examples": null
44661
+ },
44662
+ {
44663
+ "id": "v22",
44664
+ "label": "v22 migrations",
44665
+ "description": "After `migrate-from-optimus`, run the v22 migrations. The workspace did not go through `ng update`, so they are run explicitly, from the version before v22:\n\n```bash\nng update @exhaustive-ui/core --migrate-only --from=3.0.0\n```\n\nThey rewrite the templates and code for the inputs, outputs and templates removed or renamed in v22, and for the configuration options that became signals or changed name, such as `inputStyle`, now `inputVariant`. They\nreport what they cannot rewrite. The [migration guide to v22](https://exhaustive-ui.com/migration/v22) then covers the code changes: signal inputs, `model()` and signal queries in every component, OnPush change\ndetection, and the behavior and type changes.",
44666
+ "examples": null
44667
+ },
44668
+ {
44669
+ "id": "checklist",
44670
+ "label": "Checklist",
44671
+ "description": "- No `@openng/optimus-ui*` package left in any `package.json`, and the report of `migrate-from-optimus` handled.\n- `provideExhaustive`, `Exhaustive`, `ExhaustiveConfigType` and `EXHAUSTIVE_CONFIG` in place of the Optimus names.\n- With a CSS layer configured, your overrides still apply.\n- The v22 migrations run and their report handled.\n- The application compiles and its tests pass, after the code changes of the migration guide to v22.",
44672
+ "examples": null
44673
+ }
44674
+ ]
44675
+ },
44676
+ {
44677
+ "name": "v22",
44678
+ "path": "migration/v22",
44679
+ "title": "Migrating to v22",
44680
+ "description": "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.",
44681
+ "sections": [
44682
+ {
44683
+ "id": "overview",
44684
+ "label": "Overview",
44685
+ "description": "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\n`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.\n\nThis guide covers three starting points:\n\n- **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.\n- **PrimeNG v21**: switch to ExhaustiveUI with the `migrate-from-primeng` schematic, then run the v22 migrations explicitly.\n- **Optimus UI v2**, which shares the PrimeNG v21 API: swap the packages and imports, then run the v22 migrations explicitly.\n\nUpdating 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\n[changelog](https://github.com/e-xiste/exhaustive-ui/blob/main/CHANGELOG.md).",
44686
+ "examples": null
44687
+ },
44688
+ {
44689
+ "id": "prerequisites",
44690
+ "label": "Before you start",
44691
+ "description": "- **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.\n- **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.\n- **A build and test run that passes** before you start, so anything that breaks afterwards comes from the update.\n- **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.",
44692
+ "examples": null
44693
+ },
44694
+ {
44695
+ "id": "steps",
44696
+ "label": "Update steps",
44697
+ "description": "### From an ExhaustiveUI alpha or release candidate\n\nUpdate Angular, then ExhaustiveUI. Every installed `@exhaustive-ui/*` package moves to 22.0.0 together, and the migrations run.\n\n```bash\nng update @angular/core@22 @angular/cli@22\nng update @exhaustive-ui/core@22\n```\n\n### From PrimeNG v21\n\nUpdate 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\n`@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.\n\n```bash\nng update @angular/core@22 @angular/cli@22 --force\nnpm install @exhaustive-ui/core@22\nng generate @exhaustive-ui/core:migrate-from-primeng\nng update @exhaustive-ui/core --migrate-only --from=3.0.0\n```\n\nProjects 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,\nincluding the `--force` the Angular update needs while `primeng` is installed.\n\n### From Optimus UI v2\n\nOptimus 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\nCSS layer; then run the v22 migrations explicitly. The [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) details each step.\n\n```bash\nnpm install @exhaustive-ui/core@22\nng generate @exhaustive-ui/core:migrate-from-optimus\nng update @exhaustive-ui/core --migrate-only --from=3.0.0\n```\n\n### Then\n\n1. Read the report the migrations printed, see `Reviewing the report` below.\n2. Fix the TypeScript errors: most come from the Signals API and the removed TypeScript API.\n3. Check the screens that mutate data bound to a component, which no longer refresh under OnPush.\n4. Read the behavior changes, then build and run your tests.",
44698
+ "examples": null
44699
+ },
44700
+ {
44701
+ "id": "migrations",
44702
+ "label": "Automated migrations",
44703
+ "description": "`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\nrewrite safely.\n\n- **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.\n- **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`.\n- **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.\n- **renamed-templates**: the MultiSelect `removetokenicon` template becomes `chipicon`, with the same context.\n- **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.\n- **remove-dead-outputs**: removes Overlay `onAnimationStart`/`onAnimationDone` and MenubarSub `menuFocus`/`menuBlur`/`menuKeydown`.\n- **config-overlay-options-signal**: `Exhaustive.overlayOptions` is a signal. Assignments become `.set()` and reads become calls.\n- **config-input-style-to-variant**: the global `inputStyle` option becomes `inputVariant` (same values), in `provideExhaustive()`/`setConfig()` objects and on the `Exhaustive` service.\n- **removed-exports**: `Password_VALUE_ACCESSOR` becomes `PASSWORD_VALUE_ACCESSOR`; the removed `InplaceDisplay`/`InplaceContent` wrappers are dropped from imports and their elements become `<span>`.",
44704
+ "examples": null
44705
+ },
44706
+ {
44707
+ "id": "review",
44708
+ "label": "Reviewing the report",
44709
+ "description": "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.\n\n- **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.\n- **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.\n- **A Table `[(selectAll)]` two-way binding**, which relied on the renamed `selectAllChange`: bind `[selectAll]=\"selectAll\"` and `(onSelectAllChange)=\"selectAll = $event.checked\"`.\n- **A MultiSelect that already projects a `chipicon` template** next to `removetokenicon`: keep one of them.\n- **A configuration object that sets both `inputStyle` and `inputVariant` , or a receiver the migration cannot prove to be the `Exhaustive` service: set `inputVariant` only.\n- 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.\n\nCoding 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.",
44710
+ "examples": null
44711
+ },
44712
+ {
44713
+ "id": "signals",
44714
+ "label": "Code using a component instance",
44715
+ "description": "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\n`@ContentChild` decorator is left. Templates are not affected, and the migrations do not rewrite this kind of code: the compiler points at each place.\n\n- Read an input by calling it: `table.first()`, not `table.first`.\n- 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.\n- 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.\n- Outputs are `OutputEmitterRef`s: `.subscribe()` still works, `.pipe()` and the other `EventEmitter` members do not. Use `outputToObservable()` when you need an observable.\n- Public child references of a component are signal queries too, and are read with a call.\n- The global configuration is a set of signals on the `Exhaustive` service: `config.ripple.set(true)`, `config.inputVariant()`.\n\n```typescript\n// Before\n@ViewChild(Table) table!: Table;\n@ViewChild(Drawer) drawer!: Drawer;\n\nreset() {\n const first = this.table.first;\n this.table.selection = [];\n this.drawer.visible = false;\n this.config.ripple = true;\n}\n\n// After\ntable = viewChild.required(Table);\ndrawer = viewChild.required(Drawer);\n\nreset() {\n const first = this.table().first();\n this.table().selection.set([]);\n this.drawer().visible.set(false);\n this.config.ripple.set(true);\n}\n```",
44716
+ "examples": null
44717
+ },
44718
+ {
44719
+ "id": "onpush",
44720
+ "label": "OnPush change detection",
44721
+ "description": "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\nof 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.\n\nThe 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\ndata in a signal.\n\n```typescript\n// Before: the Select does not show the new option under OnPush\nthis.cities.push({ name: 'Paris', code: 'PRS' });\n\n// After: a new array\nthis.cities = [...this.cities, { name: 'Paris', code: 'PRS' }];\n\n// Or a signal, bound with [options]=\"cities()\"\ncities = signal<City[]>([]);\nthis.cities.update((cities) => [...cities, { name: 'Paris', code: 'PRS' }]);\n```\n\nTemplates 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\narray is therefore cheap, and no NG0955 or NG0956 warning comes from the library.",
44722
+ "examples": null
44723
+ },
44724
+ {
44725
+ "id": "removed-api",
44726
+ "label": "Removed TypeScript API",
44727
+ "description": "These removals have no migration: they only appear in TypeScript code, and the compiler points at each use.\n\n- `OverlayOptions.showTransitionOptions`/`hideTransitionOptions` and `DynamicDialogConfig.rtl`/`transitionOptions`: nothing read them. Use `motionOptions`.\n- `@exhaustive-ui/utils`: `classNames` becomes `cn`, `createStyleAsString` becomes `createStyleMarkup`, `createStyleTag` becomes `createStyleElement`, `mergeKeys` becomes `deepMerge`.\n- `@exhaustive-ui/styled`: `getDirective` on the theme service becomes `getComponent`.\n- 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.",
44728
+ "examples": null
44729
+ },
44730
+ {
44731
+ "id": "behavior",
44732
+ "label": "Behavior changes",
44733
+ "description": "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.\n\n### Forms\n\n- 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.\n- 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`.\n- Select: a Select inside a disabled `<fieldset>` is disabled, except inside the fieldset's first `<legend>`, as for native controls.\n- Select, MultiSelect and CascadeSelect use the SVG spinner of Button as their default loading icon, instead of the `pi-spin` icon class.\n- PickList: moving items sets `source` and `target` to new arrays and emits `sourceChange`/`targetChange`, so `[(source)]`/`[(target)]` bindings follow.\n- TreeTable: the selection change can fire once per intermediate step while a checkbox propagates.\n- DatePicker: the `data-date` attribute of day cells uses a 1-based month.\n- AutoFocus: the native `autofocus` attribute is only rendered when autofocus is on; Button and the other components no longer carry it by default.\n\n### Overlays and menus\n\n- Overlays are placed against the viewport without its scrollbars, so an overlay at the right edge no longer goes under the vertical scrollbar.\n- Tooltip honours the global `overlayAppendTo` option.\n- 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.\n- ContextMenu: showing a context menu closes any other one that is open.\n- ConfirmPopup: an `accepticon`/`rejecticon` template replaces the `acceptIcon`/`rejectIcon` class instead of rendering next to it, as in ConfirmDialog.\n\n### Accessibility markup\n\n- Stepper: the `tablist` role is on `p-step-list`. Splitter: the `separator` role is on the focusable gutter handle.\n- FocusTrap sentinels are no longer `aria-hidden`. ConfirmDialog no longer puts a `role` on the `p-dialog` host.\n- 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.\n\n### Theming and display\n\n- 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.\n- MeterGroup: meter widths use the exact percentage; labels keep the rounded value.\n- ToggleSwitch has no `size` input any more: it had no effect.",
44734
+ "examples": null
44735
+ },
44736
+ {
44737
+ "id": "types",
44738
+ "label": "Type changes",
44739
+ "description": "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.\n\n- Table `onFilter`: `filters` is typed `FilterMetadata | FilterMetadata[]`.\n- TreeTable `TreeTableLazyLoadEvent`: `first` is a `number` and `last` an optional `number`, as in `TableLazyLoadEvent`.\n- CascadeSelect: `options` is typed as an array, and the value accepts an object.\n- Dialog and ConfirmDialog: `pt.root` is typed as the options of the root element.\n- Chart `onDataSelect` emits the new exported `ChartDataSelectEvent` type.\n- `Confirmation` accepts `draggable`, and DatePicker `hourFormat` also accepts a number.",
44740
+ "examples": null
44741
+ },
44742
+ {
44743
+ "id": "checklist",
44744
+ "label": "Checklist",
44745
+ "description": "- Angular 22 installed, and `ng update` (or `--migrate-only --from=3.0.0`) run on a clean working tree.\n- Every place listed in the migration report handled.\n- The project compiles: inputs are read with a call, two-way properties written with `.set()`, removed TypeScript API replaced.\n- No `styleClass`, removed input or `pt*` alias left in templates: `validate_usage` of the MCP server can check this.\n- Screens that change data bound to a component show the change: new arrays and objects, or signals, rather than in-place mutation.\n- Behavior changes reviewed against your tests and screenshots.\n- 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.",
44746
+ "examples": null
44591
44747
  }
44592
44748
  ]
44593
44749
  },
@@ -44598,27 +44754,33 @@
44598
44754
  "description": "How to contribute to ExhaustiveUI.",
44599
44755
  "sections": [
44600
44756
  {
44601
- "id": "benefits",
44602
- "label": "Benefits",
44603
- "description": "Contributing to ExhaustiveUI comes with several benefits. Being part of an open-source project will enhance your career and open up exciting opportunities. You'll gain significant visibility in the developer community while improving yourself as a professional.",
44757
+ "id": "introduction",
44758
+ "label": "Introduction",
44759
+ "description": "ExhaustiveUI is a community-maintained Angular UI library, stewarded by e-xiste and dedicated to providing high-quality, versatile and accessible UI components that help developers build better applications faster.\n\n### Development Setup\n\nTo begin with, clone the ExhaustiveUI repository from GitHub:\n\n```typescript\ngit clone https://github.com/e-xiste/exhaustive-ui.git\ncd exhaustive-ui\n```\n\nThen run the documentation app in your local environment at `http://localhost:4200/`.\n\n```typescript\npnpm install\npnpm run dev\n```\n\n### Project Structure\n\nExhaustiveUI's project structure is organized as follows:\n\n```typescript\n- apps\n - docs // this documentation website\n - tailwind-playgrounds // Tailwind integration sandboxes\n- packages\n - core // components, directives and services\n - themes // built-in theme presets\n - styled // styled-mode theming engine\n - styles // base styles\n - tailwindcss // Tailwind CSS plugin\n - locale // i18n locales\n - motion // animation utilities\n - utils // shared helpers\n```",
44604
44760
  "examples": null
44605
44761
  },
44606
44762
  {
44607
44763
  "id": "helpneeded",
44608
- "label": "Helpneeded",
44609
- "description": "ExhaustiveUI is a community-driven project stewarded by e-xiste, and we appreciate any help you can provide. Here are some areas where you can contribute: Issue Triage Help us manage issues by; Reproducing reported bugs Clarifying issue descriptions Tagging issues with appropriate labels Sending Pull Requests We encourage you to send pull requests, especially for issues tagged with the help-needed label. Community Support Assist other users by participating in the issue tracker and GitHub discussions . Your expertise can help others solve problems and improve their experience with ExhaustiveUI.",
44764
+ "label": "Help Needed",
44765
+ "description": "ExhaustiveUI is a community-driven project stewarded by e-xiste, and we appreciate any help you can provide. Here are some areas where you can contribute:\n\n### Issue Triage\n\nHelp us manage issues by;\n\n- Reproducing reported bugs\n- Clarifying issue descriptions\n- Tagging issues with appropriate labels\n\n### Sending Pull Requests\n\nWe encourage you to send pull requests, especially for issues tagged with the `help-needed` label.\n\n### Community Support\n\nAssist other users by participating in the issue tracker and [GitHub discussions](https://github.com/e-xiste/exhaustive-ui/discussions). Your expertise can help others solve\nproblems and improve their experience with ExhaustiveUI.",
44610
44766
  "examples": null
44611
44767
  },
44612
44768
  {
44613
- "id": "introduction",
44614
- "label": "Introduction",
44615
- "description": "ExhaustiveUI is a community-maintained Angular UI library, stewarded by e-xiste and dedicated to providing high-quality, versatile and accessible UI components that help developers build better applications faster. Development Setup To begin with, clone the ExhaustiveUI repository from GitHub: Then run the documentation app in your local environment at http://localhost:4200/ . Project Structure ExhaustiveUI's project structure is organized as follows:",
44769
+ "id": "ai",
44770
+ "label": "AI Contributions",
44771
+ "description": "Contributions written with AI coding agents are welcome, on the same terms as any other: the pull request is yours. You understand the change and can answer questions about it in review, it is scoped to one problem, and it comes with\ntests that fail without the fix. The repository ships what agents need: the `@exhaustive-ui/mcp` server, the `exhaustive-ui` agent skill and the LLM docs, generated from this site.",
44616
44772
  "examples": null
44617
44773
  },
44618
44774
  {
44619
44775
  "id": "pathway",
44620
44776
  "label": "Pathway",
44621
- "description": "ExhaustiveUI offers an organization structure involving contributors and the core team: Contributor Role After a certain period of frequent contributions, a community member is offered the Contributor role. On average, it may take about three months, but the exact duration can vary depending on the individual commitment. Committer Role If a contributor actively participates in the codebase and PRs, their role may be upgraded to a Committer level, providing direct commit access to the ExhaustiveUI codebase.",
44777
+ "description": "ExhaustiveUI offers an organization structure involving contributors and the core team:\n\n### Contributor Role\n\nAfter a certain period of frequent contributions, a community member is offered the Contributor role. On average, it may take about three months, but the exact duration can vary depending on the individual commitment.\n\n### Committer Role\n\nIf a contributor actively participates in the codebase and PRs, their role may be upgraded to a Committer level, providing direct commit access to the ExhaustiveUI codebase.",
44778
+ "examples": null
44779
+ },
44780
+ {
44781
+ "id": "benefits",
44782
+ "label": "Benefits",
44783
+ "description": "Contributing to ExhaustiveUI comes with several benefits. Being part of an open-source project will enhance your career and open up exciting opportunities. You'll gain significant visibility in the developer community while improving\nyourself as a professional.",
44622
44784
  "examples": null
44623
44785
  }
44624
44786
  ]