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

🐞 - CalendarRange valueChange output property emits first found TuiDayRange without identifier #8564

Closed
2 of 9 tasks
zhd-dm opened this issue Aug 15, 2024 · 0 comments · Fixed by #8617
Closed
2 of 9 tasks
Assignees
Labels
community contribution This issue was closed by a PR from the community v3 v4 4.0 candidate

Comments

@zhd-dm
Copy link
Member

zhd-dm commented Aug 15, 2024

Playground Link

No response

Description

Hi!

I'm using the TuiCalendarRange component with presets for 30 days, a week, a month, a quarter, and a year. In certain scenarios, some of these presets can overlap. When selecting a preset, the valueChange event emits the first matching TuiDayRange without any identifier. This makes it difficult to build further logic in my application, as I need to distinguish between different presets.

Steps to Reproduce:

Set up the TuiCalendarRange component with presets for 30 days, a week, a month, a quarter, and a year.
Ensure that today is the 1st day of the month, the 1st day of the week, and the 1st day of the quarter (ex. 1 yuly 2024).
Select a preset that overlaps with others (e.g., week and a month).
Observe the emitted TuiDayRange in the valueChange event.

Expected Behavior:

The valueChange event should emit the selected TuiDayRange with an identifier or a clear way to distinguish between overlapping presets.

Actual Behavior:

The valueChange event emits the first matching TuiDayRange, making it difficult to determine which preset was selected.

Angular version

17

Taiga UI version

3.90, 4+

Which browsers have you used?

  • Chrome
  • Firefox
  • Safari
  • Edge

Which operating systems have you used?

  • macOS
  • Windows
  • Linux
  • iOS
  • Android
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community contribution This issue was closed by a PR from the community v3 v4 4.0 candidate
2 participants