fix: require pure Python forwarding shape - #693
Open
ApexWorm wants to merge 2 commits into
Open
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
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.
Problem
The Python passthrough detector relied on textual param=param matches, which labels decorated command entrypoints, functions that construct requests, and typed dataclass fixture factories as high-confidence redundant wrappers.
Fix
Parse Python modules and only report undecorated top-level functions whose body is an optional docstring plus one return that directly forwards parameters to a statically rooted, non-constructor call target. This preserves genuine lower-case forwarding aliases while rejecting multi-step functions, nested request construction, dynamic receivers, and Capitalized class-constructor factories.
Verification