Repository navigation
Expand API contract coverage and harden Patchline 0.2 - #1
Merged
Merged
Conversation
Xenrai
marked this pull request as ready for review
September 19, 2026 18:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Patchline could miss contract changes outside 200 responses and array items, and a nonexistent scan folder could incorrectly pass CI. This update compares all response statuses and media representations, follows array items and escaped local references, checks required bodies/parameters and top-level request fields across content types, and gives input failures a distinct exit code of 2.
The scanner adds Python and JS module extensions, bracket access, deterministic results, dependency/build-folder exclusions, and rejection of unsupported breaking-change kinds. Package discovery is explicit, the version is 0.2.0, and CI now covers Windows and Linux.
Validation: 46 local tests pass; the built wheel installs into an isolated environment and the documented diff/scan demo returns the expected exit codes and seven call sites. The pinned Stripe comparison reproduces 6,398 findings (18 breaking), including a previously missed removal of data[].iin. The generated report and expected totals have been updated together.
Remaining limits are documented: heuristic call-site matching, five-level traversal, no schema-composition analysis, no YAML/external references, and no complete OpenAPI compatibility proof. The expanded CI matrix must pass before merging.