You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have a swagger file with references where only path is unique but filename is not, then swagger parser will mix responses resulting in a parser result not matching actual swagger definitions.
Example:
index.yaml with responses section like below:
If we have a swagger file with references where only path is unique but filename is not, then swagger parser will mix responses resulting in a parser result not matching actual swagger definitions.
Example:
index.yaml with responses section like below:
Then both responses will be indexed with a same key resulting in only one of these is being used and other discarded.
This is because
RefUtils.computeDefinitionName()
will only use filename when computing external reference nameTested with 2.1.22 and 2.1.24
The text was updated successfully, but these errors were encountered: