[16.0][FIX] web_calendar_slot_duration: fixing behavior on slot duration #2818
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.
Convert all to float :
if we use a context like {'calendar_slot_duration': '01:30:00'} we will have on the backend a duration of 10 hour and 30 minutes instead of 1 hour and 30 minutes
And using a slot_duration > 1 hour, the calendar view will be adapted to the slot duration but has not a good presentation.
So I'm adding a possibility to adapt or not the calendar view using
adapt_view_to_slot_duration
on the context too.