Fix remote possibility to return wrong current order #183
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.
Orders' guest token is always populated thanks to a
before_create
callback on the application
layer.
However, it can be
NULL
in the database.This commit makes sure that no order is returned in two situations:
X-Spree-Order-Token
is not given, and it exists an order withNULL
guest token.X-Spree-Order-Token
is provided as an empty string, and it existsan order with an empty string as a guest token.
Being defensive against these two options leaves us on the safe side if
business rules around the guest token change at some point in
solidus-core.
This problem is similar to what is fixed in #182