Skip to content

Provide a physicalLocation on a stack frame #69

@michaelcfanning

Description

@michaelcfanning

We currently break out uri, uriBaseId, etc. on a stack frame instead of putting a physicalLocation on it. I think the reason is that we didn't see value in providing all the information in a physicalLocation (a region doesn't exactly make sense for a stack frame).

I think it might be preferable to simply have the physicalLocation object, though, with the caveat that its region data is not likely to cover a multi-line span.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions