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
Is your feature request related to a problem? Please describe.
Currently, the oasgen-provider always attempts to resolve external references ($ref) defined in Swagger files. This can cause issues when the external references are not accessible or intentionally left unresolved (e.g., for modular API definitions or when external dependencies are managed separately). There appears to be no way to skip this resolution process, which limits flexibility and may lead to failures in processing the Swagger file.
Describe the solution you'd like
I would like the ability to configure the oasgen-provider to skip the resolution of external references defined in Swagger files. This could be implemented by adding an option to the RestDefinition manifest, such as skipExternalRefs, that explicitly disables the resolution of external references.
Here is an example of how this configuration could look:
When skipExternalRefs is set to true, the oasgen-provider would process the Swagger file without attempting to resolve external references.
Describe alternatives you've considered
Pre-processing the Swagger file: Modifying the Swagger file beforehand to remove or replace external references.
Additional context
Skipping external reference resolution can be particularly useful for modular Swagger designs where some parts of the API definition are dynamically managed or resolved at runtime.
If possible, the implementation could also allow logging or warnings about skipped references, helping users debug potential issues while keeping the resolution process optional.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the
oasgen-provider
always attempts to resolve external references ($ref
) defined in Swagger files. This can cause issues when the external references are not accessible or intentionally left unresolved (e.g., for modular API definitions or when external dependencies are managed separately). There appears to be no way to skip this resolution process, which limits flexibility and may lead to failures in processing the Swagger file.Describe the solution you'd like
I would like the ability to configure the
oasgen-provider
to skip the resolution of external references defined in Swagger files. This could be implemented by adding an option to theRestDefinition
manifest, such asskipExternalRefs
, that explicitly disables the resolution of external references.Here is an example of how this configuration could look:
When
skipExternalRefs
is set totrue
, theoasgen-provider
would process the Swagger file without attempting to resolve external references.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: