feat/path conversions

[baywet]

fixes #2806

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
93.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[baywet]

@copilot we're missing a policy to map the requestBody property to a in:body parameter for the path conversion to v2

[Copilot]

@copilot we're missing a policy to map the requestBody property to a in:body parameter for the path conversion to v2

Added in c0d89d1. The new V2RequestBodyToBodyParameterPolicy maps:

• #/paths/~1items/post/requestBody → #/paths/~1items/post/parameters/0
• #/paths/~1items/post/requestBody/content/application~1json/schema → #/paths/~1items/post/parameters/0/schema
• #/paths/~1items/post/requestBody/{prop} → #/paths/~1items/post/parameters/0/{prop}

requestBody was also removed from V2UnsupportedPathPolicy.UnsupportedSegments so it's no longer returned as null.

[baywet]

@copilot the policies aren't 'rooted' in the document then they can have false positive matches. For example the V2ResponseContentUnwrappingPolicy can match an extension or schema that just happens to have a path that matches ./responses/[^/]/content/[^/]*.

Example paths that can cause incorrect path conversions: #/paths/1items/get/requestBody/content/application1json/schema/properties/responses/properties/content/properties/foo#/x-ms-sneaky-extension/additionalReference/responses/data/content/0

Attempt to root the regexes where possible (dollar sign), add additional negative tests

[Copilot]

@copilot the policies aren't 'rooted' in the document then they can have false positive matches. For example the V2ResponseContentUnwrappingPolicy can match an extension or schema that just happens to...

Addressed in c063087. Two rooting strategies were applied:

1. HTTP method anchor for operation-level keywords — V2RequestBodyToBodyParameterPolicy now requires requestBody to be immediately preceded by an HTTP method, and V2ResponseContentUnwrappingPolicy requires responses to be immediately preceded by an HTTP method. This prevents both example false positives: the schema-property responses/content inside a deep schema tree, and the #/x-ms-sneaky-extension/additionalReference/responses/data/content/0 extension path.

2. IsSchemaContext guard for the remaining policies — a new helper returns true when any prior segment is properties or additionalProperties, indicating the path has entered a JSON Schema property map. Applied to V2UnsupportedPathPolicy, V2HeaderSchemaUnwrappingPolicy, and V2ComponentRenamePolicy's inline unwrapping checks.

Added negative tests covering schema-property false positives, extension-path false positives, and component-schema paths where only the rename applies.