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
Is your feature request related to a problem? Please describe.
This is related to the problem described in #3185. When you search for rooms or resources you don't see if they are available until you pick them and open the free/busy view or save the event and let Sabre schedule the availability.
Describe the solution you'd like
As a user I would prefer that the availability is included in the details of the search results. This of course means that the currently selected time has to be factored into the search query and the server has to evaluate this property.
Describe alternatives you've considered
We fetch rooms and resources as before, but then also do a availability check like for the free/busy view and use this additional info to enhance the search result item details.
Additional context
#3183 for more details on the result items. This is likely a blocker before we can dive into this enhancement.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is related to the problem described in #3185. When you search for rooms or resources you don't see if they are available until you pick them and open the free/busy view or save the event and let Sabre schedule the availability.
Describe the solution you'd like
As a user I would prefer that the availability is included in the details of the search results. This of course means that the currently selected time has to be factored into the search query and the server has to evaluate this property.
Describe alternatives you've considered
We fetch rooms and resources as before, but then also do a availability check like for the free/busy view and use this additional info to enhance the search result item details.
Additional context
#3183 for more details on the result items. This is likely a blocker before we can dive into this enhancement.
The text was updated successfully, but these errors were encountered: