-
Notifications
You must be signed in to change notification settings - Fork 945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetch availability data #868
Conversation
|
||
return Promise.all([ | ||
dispatch(showListing(listingId)), | ||
dispatch(fetchTimeSlots(timeSlotsParams)), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed IRL, I think this call should be included when flagged somehow in config.js
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's 2 things to be changed:
- When buyr ends up to CheckoutPage, speculate and initiate calls might still throw an error related to time-slot being reserved (if that happens within few moments between redirecting to the checkout page and pressing the book button). That error needs some special handling.
- Add some flag to config.js (some marketplaces need this, others don't)
82e2ca7
to
8c2033c
Compare
Put time slots fetching behind a flag. I'll leave the error message handling along with a changelog entry to a future PR when the availability can be passed to the calendar components and this whole thing can be tied together. |
Adds availability data fetching for listing page on page load.