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 we resolve references recursively, we only want to do this for references that point outside of where we would already be resolving references. What is happening now is that extra references are being recorded in the metadata, which impacts resolution, because we are walking references already intended on being walked. Here is an example:
The reason for this is we are recursively processing the reference at #/definitions/A/allOf/0 twice, once normally and once as a result of trying to make sure we resolve references outside of where a remote reference might point.
The text was updated successfully, but these errors were encountered:
whitlockjc
changed the title
Fix for #70 breaks is too aggressive
Fix for #70 breaks creates duplicate references
Feb 2, 2016
When we resolve references recursively, we only want to do this for references that point outside of where we would already be resolving references. What is happening now is that extra references are being recorded in the metadata, which impacts resolution, because we are walking references already intended on being walked. Here is an example:
reports 3 references instead of two:
The reason for this is we are recursively processing the reference at
#/definitions/A/allOf/0
twice, once normally and once as a result of trying to make sure we resolve references outside of where a remote reference might point.The text was updated successfully, but these errors were encountered: