fix: pass validator config options when validating OpenAPI doc #132
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when initializing validator.NewValidator with a custom regex engine, that engine is not passed down to the
ValidateDocument()
function.For example:
In this case, although config.WithRegexEngine(customRegexEngine) is provided during initialization, it is not used during validation, because ValidateDocument() does not forward the option.
This PR resolves the issue by ensuring v.options.RegexEngine is passed into ValidateOpenAPIDocument using the config.WithRegexEngine option. This ensures that any custom regex engine specified during initialization is correctly applied when validating OpenAPI documents.