You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Even though we are able to set "datetime" custom field without "min" parameter, the UI component is hardcoded to allow date just 10 years before and after current year.
As far as I saw DatetimePickerComponent has just default value of "@input() yearRange = 10;" min and max paramters for custom field aren't reflected in this @input.
To Reproduce
Steps to reproduce the behavior:
Create "datetime" custom field with min: null, or some date long time in history e.g. 1500.
In Admin UI try to set any date before year 2010 (e.g. 1.1.2001) - it won't let you, and there is no mechanism to set the allowed date range of UI component.
Expected behavior
The UI component either reflects the "min" and "max" parameters in the allowed-to-set year range of dates, or there is a way to set yearRange in custom field configuration.
The text was updated successfully, but these errors were encountered:
This was just partially fixed. We are now able to input the older date by clicking previous month enough of times, howerever in select box of "Year" the oldest is still 2010.
Describe the bug
Even though we are able to set "datetime" custom field without "min" parameter, the UI component is hardcoded to allow date just 10 years before and after current year.
As far as I saw DatetimePickerComponent has just default value of "@input() yearRange = 10;" min and max paramters for custom field aren't reflected in this @input.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The UI component either reflects the "min" and "max" parameters in the allowed-to-set year range of dates, or there is a way to set yearRange in custom field configuration.
The text was updated successfully, but these errors were encountered: