Ballerina GraphQL mutation won't properly invoke when Enum is used as a parameter of the input object

[shayanmalinda]

Description:
When GraphQL mutation has a record type which contains an Enum attribute, that endpoint will not be invoked properly. It will indefinetely try to invoke the endpoint.

Steps to reproduce:

GraphQL endpoint Definition

remote function createUser(types:UserInput input) returns User|error {
    log:printInfo("Test log");
    ...
}

Record type definition of the UserInput

public type UserInput record {|
    ...
    UserType userType;
|};

Definition of the UserType enum

public enum UserType {
    OWN_CONTACT = "OWN CONTACT",
    PARTNER_CONTACT = "PARTNER CONTACT"
}

"Test log" won't logged out in above case.
Above issue won't occur when userType is defined as string userType.

Affected Versions:

2201.3.2

Suggested Assignees (optional):

@ThisaruGuruge

[ThisaruGuruge]

This is a known bug due to a Ballerina runtime API limitation. This has been fixed now and will be available with GraphQL 1.6.0 release (which will be released with Ballerina 2201.4.0: SwanLake Update 4).

Related: #3721

[github-actions]

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.