Postman cannot have a null header value #12
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
philsturgeon
force-pushed
the
feature/no-null-postman-header-value
branch
from
b836f28 to
13576bb
Compare
added 2 commits
December 6, 2017 16:31
Empty string is valid, null is invalid.
|
It would be great to add Postman's actual validation pass to the test suite too |
Author
|
@fenollp certainly something I want to do, but right now I think Postman is offering an invalid schema file. https://gist.github.com/philsturgeon/a901f1212286c8f0d389cda74706bc40 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
At work I've been generating postman collections from swagger, and a null value appeared. Uploading it to the Postman Pro API gave me a swagger error, and it turns out this same issue exists in the output.json.