-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate Postman Input and Outut #154
Open
philsturgeon
wants to merge
32
commits into
luckymarmot:develop
Choose a base branch
from
philsturgeon:feature/lint-postmana
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Validate Postman Input and Outut #154
philsturgeon
wants to merge
32
commits into
luckymarmot:develop
from
philsturgeon:feature/lint-postmana
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
Added link to documentation in README
Fixed Path Bugs in Paw Parser
added support for custom headers for api key auths
fixed pathname bug for very weird urls
…nfigs fixed missing postman loader, parser, and serializers from configs
loaders now defaults to fsResolution instead of httpResolution
Still not entirely working but its closer
Fix postman for node
The README talked a bit too much about Paw, which is not what this library is going to be used for by the community at large. It also focused on compile instructions over recommending npm/yarn installation. ALSO the compile instructions were invalid, and talked about make install (doesnt exist!).
Linked to issues where they exist, and removed CLI usage (as it does not exist).
A few forks were updating these links and causing conflicts, so lets just use local links :D
…o JonathanMontane-fork
Empty string is valid, null is invalid.
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.
Using JSON Schema parser to validate that examples for postman collection are valid for its v2 schema.
The main commit here is d304d4b, but I have a bunch of changes in my own branch. If you want this change and you want it clean, let me know and I'll clean it up, but I've not heard anything back on my other PRs.
Next steps: