-
Notifications
You must be signed in to change notification settings - Fork 61
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
fix: Consider shouldSplitItem
value from ValidateCart
mutation response
#2528
base: main
Are you sure you want to change the base?
fix: Consider shouldSplitItem
value from ValidateCart
mutation response
#2528
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
e0da991
to
325e02e
Compare
shouldSplitItem
from ValidateCart
mutation responseshouldSplitItem
value from ValidateCart
mutation response
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.
LGTM 🚀
I've tested in the starter: vtex-sites/starter.store#600
The shouldSplitItem
variable is being sent on the payload as expected ✅
discovery.config.js | payload |
---|---|
after cleaning the cache,I've tried setting shouldSplitItem: false
discovery.config.js | payload |
---|---|
What's the purpose of this pull request?
This PR intends to fix the behavior of
shouldSplitItem
value sent by through theValidateCart
mutation.Currently, the variable value is being overridden after some mutation calls due to its value not being sent back in the mutation response, so with these changes we will consider the same value set in the store config.
How to test it?
Perform actions that triggers the
ValidateCart
mutation (open/close the cart, add/remove items to/from the cart) and check if theshouldSplitItem
variable is being sent on the payload and if its value is corresponding to the one set in the store config.Starters Deploy Preview
References
Issue: #2426