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]: Cannot debug readonly records in SL 8.x and 9.x #42848

Closed
lochana-chathura opened this issue Jun 3, 2024 · 0 comments · Fixed by #42851
Closed

[Bug]: Cannot debug readonly records in SL 8.x and 9.x #42848

lochana-chathura opened this issue Jun 3, 2024 · 0 comments · Fixed by #42851
Assignees
Labels
Area/Debugger Issues related to the ballerina debugging tools Priority/High Reason/Regression The issue has introduced a regression. Team/DevTools Ballerina Developer Tooling ( CLI, Test FW, Package Management, OpenAPI, APIDocs ) Type/Bug
Milestone

Comments

@lochana-chathura
Copy link
Member

lochana-chathura commented Jun 3, 2024

Description

$subject.

import ballerina/io;

public type Rec1 readonly & record {|
    int id;
    string str;
|};

public function main() {
    Rec1 r1 = { id: 1, str: "hello" };
    io:println(r1.id); // place the debug point here
}

Consider the above simple readonly record. The record field values are not shown in the debugger.
Please refer to the below screenshot.

Screenshot 2024-06-03 at 13 58 41

Note: Field values are shown in the debugger when the readonly intersection is removed from the record.

Shows the correct information in 2201.7.1

Screenshot 2024-06-03 at 14 11 32

Affected Version(s)

SL 2201.8.0 at least.

Works in 2201.7.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Debugger Issues related to the ballerina debugging tools Priority/High Reason/Regression The issue has introduced a regression. Team/DevTools Ballerina Developer Tooling ( CLI, Test FW, Package Management, OpenAPI, APIDocs ) Type/Bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants