Fix/remove cart customer check exception #1998
Closed
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
AidasK
force-pushed
the
fix/remove-cart-customer-check-exception
branch
from
a435461
to
72b5668
Compare
AidasK
force-pushed
the
fix/remove-cart-customer-check-exception
branch
from
72b5668
to
63bf7c7
Compare
|
If a user logs in, Lunar assumes they are associated to a customer and if not throws an exception because a user must belong to a customer. We don't support users placing orders without being associated to a customer. I'm going to close this issue, but if you think this is wrong or think it could be improved, please let me know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If anonymous customer creates a cart and then tries to login it it throws an exception and page crashes. From database perspective customer can have multiple users so this check should not be performed at all.