-
Notifications
You must be signed in to change notification settings - Fork 0
chore: Per-element precision for literal destructuring #86
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
martinnaj
merged 1 commit into
master
from
mnaj-per-element-precision-for-literal-destructuring
Aug 3, 2026
+181
−17
Merged
Changes from all commits
Commits
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 |
|---|---|---|
| @@ -1 +1 @@ | ||
| 0.24.13 | ||
| 0.25.0 |
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.
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 | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 167
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 2499
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 7710
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 581
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 1184
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 7742
🌐 Web query:
microsoft typescript-go AST BindingElement struct Initializer Node source💡 Result:
In the microsoft/typescript-go project, a BindingElement is represented as a struct within the ast package [1][2][3]. This node type is part of the AST (Abstract Syntax Tree) used to represent binding elements within object or array binding patterns [2]. A BindingElement struct typically includes an Initializer field, which is an optional node (or pointer to a Node) representing the default value assigned to the binding element if the property or array element is missing or undefined during destructuring [1]. Key technical aspects include: - The Initializer field allows for default value assignment, similar to the TypeScript compiler's BindingElement interface [4][5]. - Transformer utilities in the project frequently check for the presence of this Initializer to convert binding patterns into standard assignment expressions during code generation [1]. - The node structure is designed to support both object and array destructuring, with methods like convertBindingElementToArrayAssignmentElement and convertBindingElementToObjectAssignmentElement handling the transformation of these elements [1]. - The AST node also holds other essential properties such as the Name (the binding name) and the optional PropertyName (used in object binding patterns) [1][2][3]. This implementation mirrors the TypeScript compiler's underlying AST, where BindingElement is defined as an interface that includes a name, an optional property name, an optional initializer, and a dotDotDotToken for rest elements [4][5].
Citations:
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 392
🏁 Script executed:
Repository: gooddata/gooddata-goodchanges
Length of output: 392
Include binding default initializers in the recorded span.
When
be.Initializeris present, extend the mapped span to include that expression. Otherwise,compute()inconst { a = compute() } = { a: p }andfallbackValinconst [a = fallbackVal] = [p]are excluded fromfindTaintedSymbolsByUsageand taint detection misses them.🤖 Prompt for AI Agents