#15282 new feature ()

Opened March 13, 2018 07:49PM UTC

Last modified October 25, 2018 01:45PM UTC

Check if a date is disabled on a Datepicker

Reported by: joelamos Owned by:
Priority: minor Milestone: none
Component: ui.datepicker Version: 1.12.1
Keywords: Cc:
Blocked by: Blocking:
Description

Similar tickets have been opened before, but I hope to make a new case for this feature's inclusion.

The main argument against it seems to be that we could simply name our beforeShowDay and use that to determine the state of a given date.

However, this disregards the idea of encapsulation. I shouldn't need the information I used to create an entity in order to glean info about the entity.

What if I don't have access to the validation function used to create the picker? What then?

Attachments (0)
Change History (2)

Changed March 13, 2018 08:02PM UTC by joelamos comment:1

description: Similar tickets have been opened before, but I hope to make a new case for this feature's inclusion. \ \ The main argument against it seems to be that we could simply name our beforeShowDay and use that to determine the state of a given date. \ \ However, this disregards the idea of encapsulation. I shouldn't need the information I used to create an entity in order to glean info about the entity. \ \ What if I don't have access to the validation function from my context? What then? → Similar tickets have been opened before, but I hope to make a new case for this feature's inclusion. \ \ The main argument against it seems to be that we could simply name our beforeShowDay and use that to determine the state of a given date. \ \ However, this disregards the idea of encapsulation. I shouldn't need the information I used to create an entity in order to glean info about the entity. \ \ What if I don't have access to the validation function used to create the picker? What then?

Changed October 25, 2018 01:45PM UTC by scottgonzalez comment:2

component: ui.core → ui.datepicker