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]: Invalid error message: must be resource function instead of resource_func #43815

Open
dulajdilshan opened this issue Feb 13, 2025 · 0 comments
Labels
Area/Compiler good first issue Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug userCategory/Compilation

Comments

@dulajdilshan
Copy link
Contributor

Description

Image

Steps to Reproduce

service class Person {
    resource function get age() returns int {
        do {
        } on fail error err {
            //handle error
        }
    }
}

Affected Version(s)

2201.9.2

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

@ballerina-bot ballerina-bot added needTriage The issue has to be inspected and labeled manually userCategory/Compilation labels Feb 13, 2025
@dulajdilshan dulajdilshan changed the title [Bug]: Invalid error message: must be resource functions instead of resource_func [Bug]: Invalid error message: must be resource function instead of resource_func Feb 13, 2025
@dulajdilshan dulajdilshan added Area/Compiler Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. and removed needTriage The issue has to be inspected and labeled manually labels Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Compiler good first issue Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug userCategory/Compilation
Projects
None yet
Development

No branches or pull requests

3 participants