@guildofgleks/ui 21.2.2 → 21.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -11,9 +11,9 @@ dependencies are `@angular/core`, `@angular/common` and `@angular/forms`.
11
11
 
12
12
  ## Features
13
13
 
14
- - 16 standalone components — accordion, button, checkbox, chip, dialog, icon,
15
- inputfield, multiselect, paginator, select, skeleton, slider, spinner, table, tag,
16
- toast — plus `DialogService`, `ToastService` and `ThemeService`.
14
+ - 18 standalone components — accordion, button, checkbox, chip, collapsible, dialog,
15
+ icon, inputfield, multiselect, paginator, select, skeleton, slider, spinner, table,
16
+ tag, textarea, toast — plus `DialogService`, `ToastService` and `ThemeService`.
17
17
  - Signal-based API throughout: `input()` / `output()` / `model()`, `OnPush` change
18
18
  detection, no NgModules.
19
19
  - No CDK, no Material — a small dependency footprint on top of `@angular/core`,
@@ -21,7 +21,10 @@ dependencies are `@angular/core`, `@angular/common` and `@angular/forms`.
21
21
  - Full theming through CSS custom properties: restyle any component, swap the whole
22
22
  palette, or ship light/dark and custom themes at runtime via a `data-theme` attribute.
23
23
  - `ControlValueAccessor` on every form control (checkbox, inputfield, select,
24
- multiselect, slider) — works with `formControl`, `formControlName` and `ngModel`.
24
+ multiselect, slider, textarea) — built and tested against Reactive Forms (`formControl` /
25
+ `formControlName`). The library does not use `ngModel`/`FormsModule` anywhere itself,
26
+ and template-driven usage via `[(ngModel)]` is untested — CVA makes it likely to work,
27
+ but it isn't a supported or verified path.
25
28
  - Accessible by default: keyboard navigation, ARIA attributes, WCAG AA contrast.
26
29
 
27
30
  ## Install
@@ -175,17 +178,26 @@ Google Fonts) add `@guildofgleks/ui/styles/fonts.css` as well.
175
178
 
176
179
  ## Components
177
180
 
178
- `gog-accordion`, `gog-button`, `gog-checkbox`, `gog-chip`, `gog-dialog`, `gog-icon`,
179
- `gog-inputfield`, `gog-multiselect`, `gog-paginator`, `gog-select`, `gog-skeleton`,
180
- `gog-slider`, `gog-spinner`, `gog-spinner-overlay`, `gog-table`, `gog-tag`, `gog-toast`.
181
+ `gog-accordion`, `gog-button`, `gog-checkbox`, `gog-chip`, `gog-collapsible`, `gog-dialog`,
182
+ `gog-icon`, `gog-inputfield`, `gog-multiselect`, `gog-paginator`, `gog-select`,
183
+ `gog-skeleton`, `gog-slider`, `gog-spinner`, `gog-spinner-overlay`, `gog-table`, `gog-tag`,
184
+ `gog-textarea`, `gog-toast`.
181
185
 
182
186
  Services: `DialogService`, `ToastService`, `ThemeService`.
183
187
 
184
- `gog-checkbox`, `gog-inputfield`, `gog-select`, `gog-multiselect` and `gog-slider`
185
- implement `ControlValueAccessor`, so they work with `[formControl]`, `formControlName`
186
- and `ngModel`. With a form control attached, the error message appears once the control
187
- is both touched and invalid; without one it shows for as long as `errorMessage` is
188
- non-empty, and the consumer decides when to clear it.
188
+ `gog-collapsible` is a headless expand/collapse primitive — no owned markup, no portal.
189
+ Project any element as the trigger via `gogCollapsibleTrigger` and any element as the
190
+ panel via `gogCollapsibleContent`; `[(open)]` is two-way bindable. Useful for anything
191
+ that needs an inline expanding region without the overlay behavior of `gog-select`/
192
+ `gog-multiselect` e.g. a collapsible group of links in a nav sidebar.
193
+
194
+ `gog-checkbox`, `gog-inputfield`, `gog-select`, `gog-multiselect`, `gog-slider` and
195
+ `gog-textarea` implement `ControlValueAccessor` and are built for Reactive Forms — use
196
+ `[formControl]` or `formControlName`. The library itself never imports `FormsModule` or
197
+ uses `ngModel`; `[(ngModel)]` is not tested against these components and isn't a
198
+ supported usage path. With a form control attached, the error message appears once the
199
+ control is both touched and invalid; without one it shows for as long as `errorMessage`
200
+ is non-empty, and the consumer decides when to clear it.
189
201
 
190
202
  ## License
191
203