#192 implement fallback to search body language by header 'content-type' #201
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
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.
Hallo @helloanoop,
While importing postman collections it can happen, that the language of a raw body is missing (problem of postman export)
I have implemented a fallback to search body language by header 'content-type'.
Can you please merge the fix?
It is possible to get a new release 0.14.1 with my fixes of the last days?
Postman is not usable anymore in my company, because we are not allowed to use postman accounts, because of data privacy. (All data is stored anywhere in the world.)
And we are working strong with XML.
Thanks
Mirko