This repository was archived by the owner on Sep 17, 2025. It is now read-only.
Postman cannot have a null header value #150
Open
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
changed the title
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.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Trying to upload the generated Postman file to Postman Pro gives a JSON Schema failure. Running it locally, this change removed one error. It's possible their JSON Schema is just a bit harsh, but its failing and this fixes it.