Is it possible to not throw error if corresponding $ref could not be resolved in oas-resolver.
See original GitHub issueChecklist
- Conversion: I have checked my source definition is valid OpenAPI 2.0
- Conversion: On valid OpenAPI 2.0 input, the conversion looks wrong
- Validation: I believe my source definition is valid OpenAPI 3.0.x but the validator complains
- Validation: I believe my source definition is invalid OpenAPI 3.0.x but the validator does not complain
- Linting issue
- Resolver issue
Detailed Description
While using oas-resolver I could not found a way to not throw the error if $ref
could not be resolved. Is there any way to achieve this use case where correctly defined $ref
will be resolved and wrong $ref
will be present in the result as is instead throwing error.
Other stuff
Using oas-resolver@2.3.3
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Exception is never thrown in body of corresponding try statement
A catch-block in a try statement needs to catch exactly the exception that the code inside the try {} -block can throw (or...
Read more >10 Handling PL/SQL Errors
Sometimes the error is not immediately obvious, and could not be detected until later when you perform calculations using bad data. Again, a...
Read more >Bug - Error on import google External Dependency Manager ...
Just import tgz package External Dependency Manager for Unity 1.2.166 and Firebase App 8.2.0 into blank unity project cause this error ...
Read more >throw - JavaScript - MDN Web Docs - Mozilla
The throw statement throws a user-defined exception. ... If no catch block exists among caller functions, the program will terminate.
Read more >Exception Handling in Spring MVC
When an annotated exception is thrown from a controller method, and not handled elsewhere, it will automatically cause the appropriate HTTP ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@MikeRalphson Thanks for such a quick response!
I have verified the option
ignoreIOErrors
onoas-resolver@2.5.0
and is working as expected for my use case.Many thanks for confirming.