-
-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customizing One Resolver Removes Other Default Resolvers #1315
Comments
@dillonredding Sadly, it's possible the documentation is indeed misleading on that topic. Thanks for pointing that out. There would be two ways addressing that:
|
I think this will be the way to go, as we're already planning to make resolvers more easily injectable for #1054. |
Describe the bug
In an attempt to work around #1314, I found that when overriding only the
file
$ref
resolver, the defaulthttp
andhttps
$ref
resolvers are not used and are replaced with the providedfile
$ref
resolver.To Reproduce
C:/api/openapi.yaml
:C:/api/components.yaml
:C:/dev/script.ts
:Expected behavior
According to the documentation:
I interpret this as being able to customize specific resolvers. Customizing the
file
$ref
resolver shouldn't require reimplementing the others.Environment:
The text was updated successfully, but these errors were encountered: