Skip to content

Adding some nodes to the AST subtree that prob should be there #1550

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 4 commits into from
May 3, 2024

Conversation

konradweiss
Copy link
Collaborator

We noticed that when the elements in a RangedExpression where not properly returned by SubgraphWalker.flattenAST which created issues together with other methods. I went over all nodes and tried to identify fields that should also have the @AST annotation.

They should not, if they are already part of the AST in some other subtree and are only referenced here.

Verified

This commit was signed with the committer’s verified signature. The key has expired.
NeQuissimus Tim Steinbach
…should not, if thy are already part of the AST at some other place.

Verified

This commit was signed with the committer’s verified signature. The key has expired.
NeQuissimus Tim Steinbach

Verified

This commit was signed with the committer’s verified signature. The key has expired.
NeQuissimus Tim Steinbach
…nly as an ephemeral construct that does not make it to persistency or a pass that uses the annotation

Verified

This commit was signed with the committer’s verified signature. The key has expired.
NeQuissimus Tim Steinbach
Copy link

sonarqubecloud bot commented May 3, 2024

@konradweiss konradweiss merged commit 11bccdc into main May 3, 2024
3 checks passed
@konradweiss konradweiss deleted the bugfix/ast-tree branch May 3, 2024 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants