Skip to content
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
wants to merge 32 commits into
base: develop
Choose a base branch
from

Conversation

philsturgeon
Copy link

@philsturgeon philsturgeon commented Dec 18, 2017

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:

JonathanMontane and others added 30 commits August 4, 2017 10:51
Added link to documentation in README
added support for custom headers for api key auths
…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
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
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants