Remote document cache does not handle cached errors #103
Comments
whitlockjc
added a commit
that referenced
this issue
Apr 20, 2017
The resolver was rewritten to fix numerous bugs and performance issues. The reason for this is over the years, bug fixes and features have been added on top of json-refs and its resolver logic has become crufty. The new rewrite is clean, does not reinvent the wheel and fixes many bugs. Fixes: #80, #87, #88, #89, #97, #101, #103
whitlockjc
added a commit
that referenced
this issue
Apr 20, 2017
The resolver was rewritten to fix numerous bugs and performance issues. The reason for this is over the years, bug fixes and features have been added on top of json-refs and its resolver logic has become crufty. The new rewrite is clean, does not reinvent the wheel and fixes many bugs. Fixes: #80, #87, #88, #89, #97, #100, #101, #103
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever a remote document request returns an error, we cache the error but whenever we consult the cache, we do not handle the cached error.
The text was updated successfully, but these errors were encountered: