Fixed bug that kept the date enabled when the time slot was less than 30m
This commit is contained in:
		
							parent
							
								
									bfc7cce688
								
							
						
					
					
						commit
						a28cb455f1
					
				
					 2 changed files with 10 additions and 2 deletions
				
			
		|  | @ -7,7 +7,14 @@ import getSlots from "@lib/slots"; | |||
| dayjs.extend(utc); | ||||
| dayjs.extend(timezone); | ||||
| 
 | ||||
| const DatePicker = ({ weekStart, onDatePicked, workingHours, organizerTimeZone, inviteeTimeZone }) => { | ||||
| const DatePicker = ({ | ||||
|   weekStart, | ||||
|   onDatePicked, | ||||
|   workingHours, | ||||
|   organizerTimeZone, | ||||
|   inviteeTimeZone, | ||||
|   eventLength, | ||||
| }) => { | ||||
|   const [calendar, setCalendar] = useState([]); | ||||
|   const [selectedMonth, setSelectedMonth]: number = useState(); | ||||
|   const [selectedDate, setSelectedDate]: Dayjs = useState(); | ||||
|  | @ -43,7 +50,7 @@ const DatePicker = ({ weekStart, onDatePicked, workingHours, organizerTimeZone, | |||
|         date.endOf("day").isBefore(dayjs().tz(inviteeTimeZone)) || | ||||
|         !getSlots({ | ||||
|           inviteeDate: date, | ||||
|           frequency: 30, | ||||
|           frequency: eventLength, | ||||
|           workingHours, | ||||
|           organizerTimeZone, | ||||
|         }).length | ||||
|  |  | |||
|  | @ -128,6 +128,7 @@ export default function Type(props): Type { | |||
|               workingHours={props.workingHours} | ||||
|               organizerTimeZone={props.eventType.timeZone || props.user.timeZone} | ||||
|               inviteeTimeZone={timeZone()} | ||||
|               eventLength={props.eventType.length} | ||||
|             /> | ||||
|             {selectedDate && ( | ||||
|               <AvailableTimes | ||||
|  |  | |||
		Loading…
	
		Reference in a new issue
	
	 Alex van Andel
						Alex van Andel