fix(driver): allow undefined extensions key in Magento graphql responses #3087
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Once you upgrade to v2.4.6 you will see errors like
Cannot read properties of undefined (reading 'category')
when Magento throws certain kinds of error.Fixes: N/A
What is the new behavior?
In Magento versions that support GraphQl prior to v2.4.6 there was a key errors called "extensions" that contained an error code indicating what kind of error you received. For whatever reason, in v2.4.6 they removed this. This PR allows this
extensions
key to not exist when it used to always exist.Does this PR introduce a breaking change?
Other information