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
When external referenced components have the same name but different definitions, only the first is considered, the rest seem to be ignored. This seems to be because of the way the JSON pointers are used to derive the component name in Refutils.
RefUtils.java
if (definitionPath != null) { //the name will come from the last element of the definition path
"the name will come from the last element of the definition path" - I couldn't find any documentation as to why this is done, nor did I see any mention of this in this spec.
This could likely cause issues as the definitions with same names are allow if the it is provided in-line.
When external referenced components have the same name but different definitions, only the first is considered, the rest seem to be ignored. This seems to be because of the way the JSON pointers are used to derive the component name in Refutils.
RefUtils.java
"the name will come from the last element of the definition path" - I couldn't find any documentation as to why this is done, nor did I see any mention of this in this spec.
This could likely cause issues as the definitions with same names are allow if the it is provided in-line.
P.S: Originally identified by @crankydillo.
openapi.json
external_ref1.json
external_ref_2.json
Main.java
The text was updated successfully, but these errors were encountered: