Fix(Calendar): Improve type declaration using generic types with default parameters (Fixes #7555)

[iamkyrylo]

Related Issue

Closes #7555
Fix #6583

Summary

This PR implements the proposed improvement by replacing type overloading with generic types for CalendarProps. It addresses the problem with dynamically managing selectionMode as discussed in the issue.

Screenshots

I've checked the solution by creating a small wrapper inside the project. Here is a screenshot where you can see that TypeScript correctly defines the onChange event type based on the passed selectionMode.

Default (single):

Multiple:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Updated (UTC)
primereact	⬜️ Ignored (Inspect)	Visit Preview	Jan 3, 2025 10:47am
primereact-v9	⬜️ Ignored (Inspect)	Visit Preview	Jan 3, 2025 10:47am

[melloware]

Interesting. Does this break backwards compatibility?

[iamkyrylo]

Interesting. Does this break backwards compatibility?

No, it shouldn't break anything. Previously, only CalendarProps were exposed, so users won't need to update their code, I believe. But it depends on how they applied it 🤷‍♂️

TS can still infer the onChange event and value types automatically based on the selectionMode value. This means you don't need to explicitly pass TMode type, like Calendar<TMode>. The key difference is that TS now directly uses the provided value instead of analyzing multiple type overloads.

[melloware]

Thanks!

[melloware]

This also fixes #6583