Fix: Remove SchemaUriResolver and check in schema.json instead #273
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
Codecov Report
@@ Coverage Diff @@
## master #273 +/- ##
============================================
+ Coverage 80% 87.03% +7.03%
+ Complexity 39 35 -4
============================================
Files 3 2 -1
Lines 175 162 -13
============================================
+ Hits 140 141 +1
+ Misses 35 21 -14
Continue to review full report at Codecov.
|
|
Great :-) |
This was referenced Dec 18, 2019
Merged
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.
This PR
SchemaUriResolverand checks inschema.jsoninsteadFixes #254.
Replaces #255.
💁♂ This picks up the original idea of @drupol (see #170) to check in the schema - I believe this is the best approach for now. In the meanwhile I can sort something out using GitHub actions to keep
schema.jsonupdated.