Thomas Sapelza
Thomas Sapelza
I'm using the function-based guard for a half year now, you could do it like follows: ```js import { CanMatchFn, Router, UrlTree } from '@angular/router'; import { inject } from...
Same with Quarkus `3.10.1`
I know, but in my case I need the whole `SelectItem` object or at least the `SelectItem.value` object, not only the label (the label is a computed field as you...
@yorickp your workaround works. Maybe @sandrotonon will look into his PR again and fix this issue.
@joinsaturn I didn't use `optionValue` or `optionValueFn` with `optionLabel` when updating to PrimeNG 17.15.0, I also never used the `field` input property, still, my AutoComplete completely stopped working as shown...
@cetincakiroglu can be closed if https://github.com/primefaces/primeng/issues/14721 is done.
@cetincakiroglu you can close this issue, it was fixed in #14721
My current workaround is the following, remove the input binding `[defaultDate]` from the template and set the internal `_defaultDate` in the `AfterViewInit` lifecycle. See [StackBlitz - PrimeNG CalendarReactiveFormsDemo [defaultDate] workaround](https://stackblitz.com/edit/ukbf3f-wjp5bt?file=src%2Fapp%2Fdemo%2Fcalendar-reactive-forms-demo.html,src%2Fapp%2Fdemo%2Fcalendar-reactive-forms-demo.ts)...
@cetincakiroglu this is still an issue with PrimeNG v17.18.9
Could be related to https://github.com/primefaces/primeng/issues/15140 but there the `[formControlName]` was passed wrong.