Recursively resolve definitions in remote schemas #733
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
submitteddenied
commented
Mar 3, 2017
| self.refs[url] = response; | ||
| self._getDefinitions(self.refs[url]); |
There was a problem hiding this comment.
For clarity in the summary, this is the only "real" code change
campearce
approved these changes
May 9, 2017
btsimonh
pushed a commit
to btsimonh/json-editor
that referenced
this pull request
May 26, 2021
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 (partially) resolves #408 but may lead to issues where
definitionsin remote schemas clobber those with the same name in local (or earlier) schemas.PS: Sorry about all the whitespace changes, add
?w=1to the URL to get a cleaner diff :)