Update fulfillmentInboundV0.json #5
Closed
Conversation
This file contains hidden or 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
fixed a typo swagger 2.0 was not supporting $ref enum reference in query parameter of array type
|
I was also going to mention this, having the same error messages as well. Confirmed @BilalHasanKhan pull request fixed my issues. If I recall correctly, I was receiving these same errors in other models too. |
|
Thank you for submitting this pull request @BilalHasanKhan. Our team has fixed the issue in our internal pipeline and pushed the fix in 542c2a9. |
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.
fixed a typo
swagger 2.0 was not supporting $ref enum reference in query parameter of array type
*Issue #, if available:*4
Description of changes: fixed Markeplace typo to Marketplace in InboundShipmentRequest in required array
/fba/inbound/v0/shipments/get parameter ShipmentStatusList update to comply for generating client with 2.0 specification
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.