You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a p-calendar using a formControlName and using the "year" view, the component does not display the years. and receives the following error:
ERROR TypeError: Y.getFullYear is not a function
at an.isYearSelected (calendar.ts:1680:56)
my example:
Environment
I am seeing this when running ng serve on localhost
Reproducer
No response
Angular version
17
PrimeNG version
16.0.2
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.9.0
Browser(s)
chrome
Steps to reproduce the behavior
Add the example code from primeng website version 17 beta to form using a formControlName instead of [(ngModel])
Expected behavior
No response
The text was updated successfully, but these errors were encountered:
We have the same problem with a calendar in the range selection mode.
The problem is in the isYearSelected(year: number) function of the calendar.ts. I will open a PR for this
cetincakiroglu
added
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
and removed
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Sep 26, 2024
Describe the bug
When adding a p-calendar using a formControlName and using the "year" view, the component does not display the years. and receives the following error:
Environment
I am seeing this when running ng serve on localhost
Reproducer
No response
Angular version
17
PrimeNG version
16.0.2
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.9.0
Browser(s)
chrome
Steps to reproduce the behavior
Add the example code from primeng website version 17 beta to form using a formControlName instead of [(ngModel])
Expected behavior
No response
The text was updated successfully, but these errors were encountered: