Fix for OpenAPI Component Properties, Server Endpoint, and Path Filtering Issues #1420
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.
Description:
This pull request addresses several issues related to the OpenAPI component schema properties, server endpoints, and path filtering. These changes are related to the issues raised in Issue #1419.
Changes made:
Support for additional properties in
New-PodeOAComponentSchemaProperty
:$Example
,$Deprecated
,$Required
,$Nullable
,$ReadOnly
, and$WriteOnly
properties, which were previously missing.Fix for
Add-PodeOAServerEndpoint
:Path Filtering for OpenAPI descriptions:
/api/v3
/api/v2/test
will now be excluded from the OpenAPI description, while valid paths like/api/v3/test
will be retained.Issue reference: