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

Calendar with dateformat "dd.mm.y" 01.01.35 -> 01.01.1935 #16093

Closed
hugograf opened this issue Jul 24, 2024 · 1 comment
Closed

Calendar with dateformat "dd.mm.y" 01.01.35 -> 01.01.1935 #16093

hugograf opened this issue Jul 24, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@hugograf
Copy link
Contributor

Describe the bug

When entering a date with the dateFormat “dd.mm.y”, the century 1900 is used once and 2000 the other time. Entering “31.12.34” results in 31.12.2034 and entering “01.01.35” results in 01.01.1935. We only want dates in the range 01.01.00 - 31.12.99 which should result in 01.01.2000 - 31.12.2099. Have I missed something and this should be configured with parameters?

Environment

Latest 17-PrimeNG and Angular 17 version.

Reproducer

https://stackblitz.com/edit/mggu44-ksc5ad

Angular version

17.x.x

PrimeNG version

17.x.x

Build / Runtime

Angular CLI App

Language

ALL

Node version (for AoT issues node --version)

20.10

Browser(s)

No response

Steps to reproduce the behavior

  1. Enter 01.01.35 in calendar and see January 1935
  2. Enter 31.12.34 in calendar and see December 2034

Expected behavior

  1. Enter 01.01.35 in calendar and see January 2035
  2. Enter 31.12.34 in calendar and see December 2034
@hugograf hugograf added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jul 24, 2024
@mertsincan
Copy link
Member

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,

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

2 participants