Make Patchline easy to try and correct composition false positives - #2
Merged
Merged
Conversation
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.
New visitors previously had to clone the project before they could try it, and the Stripe example overstated field removals when a response changed to an anyOf union. This release adds an installed offline demo and corrects that report before promoting the project.
patchline demouses bundled OpenAPI 3 specs and the real diff/scanner.--version, release installation instructions, a copyable CI recipe, contributor guidance, issue templates, and package links make it easier to evaluate and adopt.Composition changes now produce REVIEW findings and block the diff gate without claiming individual fields disappeared. New composed fields remain additive, unrelated field removals still show up, and parent compositions suppress misleading child findings. JSON consumers must accept the new REVIEW severity and summary.review field.
Validation: 55 tests pass locally, the pinned Stripe report reproduces four breaking field removals plus one manual review (6,380 additive), and the wheel installs and runs the demo in an empty temporary environment. CI runs the installed-wheel smoke test on Windows/Linux with Python 3.10/3.12. Remaining analysis limits are documented.
After CI passes, publish v0.3.0 with the verified wheel so the versioned installation link resolves.