[Bug]: Client declarations with @display annotation will miss the CLIENT qualifier in the SemanticAPI

[kanushka]

Description

Client/Endpoint declarations with @display annotation will miss the CLIENT qualifier in the SemanticAPI types

Steps to Reproduce

Ballerina source

import ballerina/http;

service /abc on new http:Listener(9090) {

    http:Client nrmlEp; // Client without display annotation

    @display {
        label: "HTTP client",
        id: "InternalClient-b704fd5e-06b8-47df-89fe-6c462b5cdf4e"
    }
    http:Client annoEp; // Client with display annotation    

    function init() returns error? {
        self.annoEp = check new annoEp("http://example.com/");
        self.nrmlEp = check new nrmlEp("http://example.com/");
    }

    resource function get repos(string orgName, int max = 5) returns string|error? {

    }

}

In the above example, sematicAPI will give the CLIENT qualifier for the nrmlEp client node. But for the annoEp client node will not get the CLIENT qualifier. instead of it will get PUBLIC and SERVICE qualifiers. It seems the node with @display annotation will miss the CLIENT qualifier.

Optional<TypeSymbol> typeSymbol = this.semanticModel.type(node.lineRange());
TypeSymbol typeDescriptor = typeSymbol.get();

TypeSymbol rawType = typeDescriptor.typeKind() == TypeDescKind.TYPE_REFERENCE
        ? ((TypeReferenceTypeSymbol) typeDescriptor).typeDescriptor() : typeDescriptor;

ObjectTypeSymbol objectTypeSymbol = (ObjectTypeSymbol) rawType;

objectTypeSymbol.qualifiers()

// nrmlEp -> PUBLIC, CLIENT
// annoEp -> PUBLIC, SERVICE

Affected Version(s)

2201.3.2, 2201.4.0

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