validRange option starting mid-day causes entire day to appear disabled.
See original GitHub issuevalidRange: function(nowDate) {
return { start: nowDate.clone().add(1, 'hours'), end: nowDate.clone().add(3, 'days') } ;
}
Using the validRange option shown above causes today to receive the background class “fc-disabled-day” and be greyed out. This is not accurate, any slots after one hour from now should not appear disabled.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
validRange - Docs - FullCalendar
Dates outside of the valid range will be grayed-out. The user will not be able to drag or ... The validRange property can...
Read more >DBMS_SCHEDULER - Oracle Help Center
For example, a repeat_interval of FREQ=MONTHLY;INCLUDE=HOLIDAY executes only on holidays and not on the month/day defaults retrieved from the start date.
Read more >Cisco Wireless LAN Controller Configuration Guide, Release 7.3
The controller saves your configuration, reboots, and prompts you to log on. Configuring the Controller—Using the CLI Configuration Wizard.
Read more >Show all date outside validarange in fullcalender
Since you set up the end date with today, so it's normal. Just remove the end: new Date() of validRange: . You can...
Read more >User's Guide for the AERMOD Meteorological Preprocessor ...
This user's guide provides instructions for setting up and running the ... The pathway identifier appears on a line by itself followed by...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It does work for constraining what is selectable. In my example, you can still select today, but only an hour in the future.
I see now the documentation is only concerned with dates, however the last example does show using a Moment object, which is what I used.
I would think this is a commonly desired feature, to not allow creating events in the past, even if it’s earlier today…?
Thanks for the report.
It appears that validRange only works for date ranges, not for time ranges. The docs don’t mention anything about using times in the ranges so it seems that would be a new feature.