Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CalendarModule: problem to order more than 12 months #14654

Closed
FerViaEmi opened this issue Jan 29, 2024 · 4 comments
Closed

CalendarModule: problem to order more than 12 months #14654

FerViaEmi opened this issue Jan 29, 2024 · 4 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@FerViaEmi
Copy link

Describe the bug

Dear team,

I am using CalendarModule component "primeng":"^15.3.0", in "@angular/common":"^15.0.0", "@angular/core":"^15.0.0".

I need to load the next 13 months from now but the month load fails when the current month is November or December. For the rest of the months, the process works.

Do you have this scenario identified, do you have a proposed solution?

Example of failed configuration:

Month Picker
november_calendar

Environment

development environment

Reproducer

https://stackblitz.com/edit/primeng-calendar-demo-k8gckd?file=src%2Fapp%2Fapp.component.ts,src%2Fapp%2Fapp.component.html

Angular version

15.0.0

PrimeNG version

15.3.0

Build / Runtime

Angular CLI App

Language

ALL

Node version (for AoT issues node --version)

8.3.0

Browser(s)

all

Steps to reproduce the behavior

No response

Expected behavior

the expected behaviour is to be able to recover the next 13 months without error for the months of November and December. The error is only reproducible for these two months.

@FerViaEmi FerViaEmi added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 29, 2024
@FerViaEmi
Copy link
Author

Hello,

any news about this issue?

thank you.

@egarciade
Copy link

Hi.
Have you been able to check the issue?
Please is very important for us
Thanks

@mehmetcetin01140
Copy link
Contributor

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

@DrochCH
Copy link

DrochCH commented Dec 19, 2024

Are you aware that this error persists 3 years later?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

4 participants