[Bug]: Incorrect handling of reserved keyword in Ballerina data mapping generation.

[VellummyilumVinoth]

Description

When generating data mappings in Ballerina, the version field is incorrectly treated as a reserved keyword. Instead of generating the mapping as version: patient.version, the system produces an incorrect mapping like 'version: patient.'version, which is syntactically invalid. This causes the code to fail during execution or compilation.

Steps to Reproduce

1. Define Ballerina code

public function mapPatientToUsCore(Patient patient) returns Patient => {
   
};

public type Patient record {
    string patientType;
    string patientId;
    string version;
};

2. Generate data mappings using the defined structure.

3. Observe that the generated mapping incorrectly escapes the version field as 'version: patient.'version instead of the correct format version: patient.version.

public function mapPatientToUsCore(Patient patient) returns Patient => {
    patientType: patient.patientType,
    patientId: patient.patientId,
    'version: patient.'version
};

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

[MaryamZi]

version used to be a keyword, adding the quote may be related to that.

But, it shouldn't fail and doesn't seem to fail for me either. Where/how does it fail?

[VellummyilumVinoth]

Thanks Ack. This issue is not related with CompilerFE.

This is AI data mapper bug. We will fix it.

[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.

[VellummyilumVinoth]

Reason/Other