This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Fix: Circular dependency issue with sibling schemas/definitions. #375
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.
fix Azure/autorest#3630
When a model is following the pattern
$ref and Sibling Elements
described here https://swagger.io/docs/specification/using-ref/This is causing a circular dependency issue because the model(with the properties) gets removed and the model with the reference get the ref updated to itself.
The solution is to figure out which of the 2 models to delete(The one not being a ref)
Todo: