-
Notifications
You must be signed in to change notification settings - Fork 0
fix(ownts): literal-proof useEffect-парсер + строгий матчинг release для addEventListener #145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| // Parser-hardening cases (CodeRabbit): string literals must not truncate bodies or | ||
| // split deps, deps brackets nest, and a listener is released only by a matching | ||
| // target+handler+options removeEventListener. Run: | ||
| // python frontend/ownts/ownts.py frontend/ownts/examples/EffectHardening.tsx --check | ||
| // Expect exactly: OWN001 (the options-dropped listener) + EFF001 (the object dep). | ||
| import { useEffect } from "react"; | ||
|
|
||
| export function Hardening({ id }: { id: string }) { | ||
| // A string with commas and braces must not truncate the body or split the deps; | ||
| // the timer IS cleared, so this effect leaks nothing. | ||
| useEffect(() => { | ||
| const t = setInterval(() => fetch("/a,b,{c}"), 1000); | ||
| return () => clearInterval(t); | ||
| }, [id]); | ||
|
|
||
| // Listener added WITH capture, but cleanup drops the option -> different listener, | ||
| // still leaks (one OWN001). | ||
| useEffect(() => { | ||
| window.addEventListener("scroll", onScroll, true); | ||
| return () => window.removeEventListener("scroll", onScroll); | ||
| }, []); | ||
|
|
||
| // Nested-bracket dep parses (`items[0]` stays one entry); the object literal dep | ||
| // is unstable + IO -> exactly one EFF001 (items[0] is not identifier-like: silent). | ||
| const filters = { id }; | ||
| useEffect(() => { | ||
| fetch("/x"); | ||
| }, [filters, items[0]]); | ||
|
|
||
| return <div>hardening</div>; | ||
| } |
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Expression-bodied cleanup with an options object is mis-spanned, causing false-positive leaks.
brace = mbody.find("{", m.end())searches arbitrarily far for the cleanup block's{. For a single-expression cleanup whoseremoveEventListenerpasses an options object — exactly the case this PR targets — the{of the options literal is found instead:return () => el.removeEventListener("scroll", onScroll, {capture: true})_match_blockthen ends the span at the options}, truncating the trailing). The resultingcleanup_ono longer parses via_LISTENER(which requires a closing)), so_listener_callreturnsNone,_is_releasedreturnsFalse, and a correctly-released listener is reported as a leak. Block-bodied cleanups are unaffected; only expression bodies containing braces break.Detect a block only when the first non-whitespace char after
=>is{:🐛 Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents