[GH-ISSUE #559] javascript: finish converting property-name readers and consolidate binding resolution #285

Closed
opened 2026-10-15 18:23:27 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/559

Remaining scope

PR #538 now shares unshadowed-global recognition and corrects with, eval, switch and static-block scope handling. Remaining findings are raw property readers in javascriptStaticAnalysisHelpers, repeated assigned-result binding detection across effect collectors, and lost links for destructured results. Resolve projection semantics honestly instead of treating every destructured binding as the entire result. Use one syntax-aware property rule and consolidate equivalent containment/readers.

Verification

Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable.

This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/559 ## Remaining scope PR #538 now shares unshadowed-global recognition and corrects with, eval, switch and static-block scope handling. Remaining findings are raw property readers in javascriptStaticAnalysisHelpers, repeated assigned-result binding detection across effect collectors, and lost links for destructured results. Resolve projection semantics honestly instead of treating every destructured binding as the entire result. Use one syntax-aware property rule and consolidate equivalent containment/readers. ## Verification Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable. This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.
bsakaguchi 2026-10-15 18:23:27 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#285
No description provided.