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

Component: Calendar timeOnly selectionMode="range" #13884

Closed
pclancysc opened this issue Oct 14, 2023 · 1 comment
Closed

Component: Calendar timeOnly selectionMode="range" #13884

pclancysc opened this issue Oct 14, 2023 · 1 comment
Labels
Status: Discussion Issue or pull request needs to be discussed by Core Team Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible Type: New Feature Issue contains a new feature or new component request

Comments

@pclancysc
Copy link

Describe the feature you would like to see added

The Calendar component has an existing selectionMode property. When [timeOnly]=true the selectionMode property is ignored.

Ideally allow a range of times to be selected in this mode.

e.g.
09:00 to 17:00

Is your feature request related to a problem?

I'ts not documented that the selectionRange property only applies to dates

Describe the solution you'd like

Extend current function to show two time pickers side by side. Validate end time > start time.

Describe alternatives you have considered

No response

Additional context

No response

@pclancysc pclancysc added Status: Discussion Issue or pull request needs to be discussed by Core Team Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible Type: New Feature Issue contains a new feature or new component request labels Oct 14, 2023
@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,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Discussion Issue or pull request needs to be discussed by Core Team Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible Type: New Feature Issue contains a new feature or new component request
Projects
None yet
Development

No branches or pull requests

2 participants