Rewrote the whole damn thing aaghghhghg #6
Merged
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
|
Crap I still forgot to cover contract testing. |
|
Added contract testing :D |
hskrasek
approved these changes
May 31, 2018
|
Thanks @hskrasek! Cant believe there are no glaring typos thats the first time ever. |
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.
Now that the divergence issues are somewhat solved, and the ideal workflow kinda exists, we dont have to point out things then awkwardly mumble about caveats later.
This new approach to the talk loudly proclaims about using both OpenAPI and JSON Schema, points out which is good at what, identifies the caveats, and provides solutions to using both happily.
If you wanna see this talk when its done, shove your GDPR-appproved PII into this form: http://bit.ly/2GXrEas