Skip to content
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

[Bug]: nodeFinder.typeOf() returns null as BLangNode for annotation fields #41186

Closed
mindula opened this issue Aug 10, 2023 · 2 comments · Fixed by #41809
Closed

[Bug]: nodeFinder.typeOf() returns null as BLangNode for annotation fields #41186

mindula opened this issue Aug 10, 2023 · 2 comments · Fixed by #41809
Assignees
Labels
Area/SemanticAPI Semantic API Related Issues #Compiler Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug
Milestone

Comments

@mindula
Copy link
Contributor

mindula commented Aug 10, 2023

Description

Consider the following scenario where we're trying to get completions for annotation field,

annotation StringConstraints String on type, record field;
type ConstraintRecord record {|
    anydata value;
    string message;
|};

type StringConstraints record {|
    int|record{| *ConstraintRecord; int value; |} length?;
|};

@String {
    length : {<cursor>} 
}
type TestString string;

here, we get null as the bLangNode.

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

@mindula mindula added Type/Bug Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. labels Aug 10, 2023
@mindula
Copy link
Contributor Author

mindula commented Aug 10, 2023

Related discussion #40668 (comment)

Copy link

github-actions bot commented Dec 8, 2023

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@KavinduZoysa KavinduZoysa added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Dec 8, 2023
@nipunayf nipunayf added this to the 2201.9.0 milestone Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/SemanticAPI Semantic API Related Issues #Compiler Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants