fix: generated $ref schemas when $refed with different descriptions
#252
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
🦋 Changeset detectedLatest commit: f85963d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
toomuchdesign
force-pushed
the
fix-refs-with-different-description
branch
from
e0a2963 to
de64ea6
Compare
toomuchdesign
changed the title
$ref schemas when $refed with different descriptions
toomuchdesign
force-pushed
the
fix-refs-with-different-description
branch
from
de64ea6 to
6dbca05
Compare
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.
What kind of change does this PR introduce?
Bug fix
What is the current behaviour?
Same
$refdeclared with differentdescriptionprop not being imported properlyWhat is the new behaviour?
$refgetting imported as expected no matter their descriptionDoes this PR introduce a breaking change?
No
Other information:
Please check if the PR fulfills these requirements: