Fix error when parsing response for AssignedFulfillmentOrder #235
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
paulomarg
force-pushed
the
fix_assigned_fulfillment_order_parse_error
branch
from
5bdce1f to
312b780
Compare
mkevinosullivan
approved these changes
Jan 4, 2023
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.
WHY are these changes introduced?
There was an error in the
AssignedFulfillmentOrderREST resource, because it was expecting the JSON response to contain aassigned_fulfillment_orderfield, but in reality we get backfulfillment_order.WHAT is this pull request doing?
Enabling resources to override the expected field, and updating the auto-generated resources to fix the issue with
AssignedFulfillmentOrder.Non-automatic changes: 4042032
Type of change
Checklist