Use dayCountAvailableForBooking config in FieldDateAndTimeInput #129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use dayCountAvailableForBooking config instead of hard-coded value in FieldDateAndTimeInput so that it matches the date range that is used in react-dates components.
Earlier the dayCountAvailableForBooking was set to 90 but the MAX_TIME_SLOTS_RANGE was 180 and the calendar looked broken because after the first 3 months the timeslots appeared as blocked. Also, if you selected the date far enough in the future, checking the timeslots broke and all the dates seem to be available.
If the dayCountAvailableForBooking and MAX_TIME_SLOTS_RANGE is the same, showing the timeslots works correctly. Here's both 90 and 180 days options:
And since there's the limitation that by default Stripe is holding funds up to 90 days from the moment they are charged, I think keeping the default range in 90 would be the best solution.