This repository has been archived by the owner on Jul 24, 2020. It is now read-only.
[1449] Fix cart availability validation [v5.5] #1451
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Resolves #1449 - ensures that checked-out reservations are also taken into account
|
Deployed to DEV and verified that this fixes the issue. As this is literally a one-word fix, I'm pretty comfortable merging this without further review but I would appreciate it if someone could manually check this out and make sure that this fixes the availability validation before I do. Thanks! |
|
I replicated the bug on release v5.5 and confirmed that this fixes the issue. |
|
Great thanks! It was also verified on DEV by the bmec folks. I'll merge, tag, and release shortly and request a PROD deployment. |
orenyk
added a commit
that referenced
this pull request
Jan 24, 2016
[1449] Fix cart availability validation
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #1449 for release-v5.5