Summary

Fixes #767 - Resolves a bug where comparing identical OpenAPI specs incorrectly reported differences when an exploded object parameter's name matched a property name within its own schema.

Problem

When running oasdiff diff on identical files, the tool incorrectly reported modifications in cases where:

• A parameter has an exploded object schema (e.g., explode: true)
• The parameter name matches a property name within that parameter's schema
• Example: A parameter named query containing a schema with a property also named query

This caused false positive diffs showing type changes and deleted properties that didn't actually exist.

Root Cause

The exploded parameter semantic equivalence matching logic (introduced in PR #744) was checking if a parameter's name matched properties in exploded object schemas. However, it didn't exclude the case where the parameter being checked was itself an exploded object parameter, leading it to match against properties in its own schema.

Solution

Added a check in matchExplodedWithSimple() to skip parameters that are themselves exploded object parameters when searching for simple parameters to match with exploded parameters. This ensures we only match truly simple parameters with exploded parameters, not exploded parameters with themselves.

Changes

• diff/parameters_diff_by_location.go: Added check to filter out exploded object parameters from the "simple" parameter list before matching
• diff/parameters_diff_by_location_test.go: Added regression test TestIssue767_ExplodedParamWithSameNameProperty
• data/explode-params/issue-767.yml: Added test fixture demonstrating the bug scenario

Testing

• ✅ New regression test passes
• ✅ All existing tests pass
• ✅ Verified fix resolves the issue: oasdiff diff test.yml test.yml now correctly returns no diff

Test plan

• Run full test suite: go test ./...
• Verify regression test: go test ./diff/... -run TestIssue767
• Manual verification with issue-767.yml fixture

🤖 Generated with Claude Code