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]: No signature help for client resource access actions #38967

Closed
malinthar opened this issue Dec 6, 2022 · 2 comments
Closed

[Bug]: No signature help for client resource access actions #38967

malinthar opened this issue Dec 6, 2022 · 2 comments
Assignees
Labels
Area/SignatureHelp Issues related to Language Server Signature Help implementation Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/LanguageServer Language Server Implementation related issues. #Compiler Type/Bug userCategory/Editor

Comments

@malinthar
Copy link
Contributor

Description

Consider the following source.

client class MyClient {

    resource function get user/[int id](string param1, string param2) returns json {
        return {};
    }
}

public function abc() returns error? {

    MyClient cl = new ();

    cl->/user/[0](<cursor>)
}

There no signature help for the param1 and param2 at the depicted cursor position.

Steps to Reproduce

No response

Affected Version(s)

2201.3.x

OS, DB, other environment details and versions

No response

Related area

-> Editor

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

@malinthar malinthar added Type/Bug Team/LanguageServer Language Server Implementation related issues. #Compiler labels Dec 6, 2022
@malinthar malinthar added the Area/SignatureHelp Issues related to Language Server Signature Help implementation label Dec 6, 2022
@ballerina-bot ballerina-bot added needTriage The issue has to be inspected and labeled manually userCategory/Editor labels Dec 6, 2022
@malinthar malinthar removed the needTriage The issue has to be inspected and labeled manually label Dec 6, 2022
@malinthar malinthar self-assigned this Apr 28, 2023
@malinthar
Copy link
Contributor Author

Closing as fixed with #39958

@github-actions
Copy link

github-actions bot commented May 2, 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.

@malinthar malinthar added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/SignatureHelp Issues related to Language Server Signature Help implementation Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/LanguageServer Language Server Implementation related issues. #Compiler Type/Bug userCategory/Editor
Projects
Archived in project
Development

No branches or pull requests

2 participants