Skip to content

Try to match both original and compiled path when determining instrumentation eligibility #182

@dividedmind

Description

@dividedmind

Currently, in the presence of source maps, only the original source path (with some exceptions) is matched with the package paths configured in appmap.yml.

This can be too restrictive; if trying to trace third-party code, for example, the user usually doesn't care about the original source directory structure but wants to be able to specify the compiled code path in appmap.yml and have it instrumented (even when there is a problem with handling the sourcemap or the map itself, cf. #181).

My intuition is trying to match BOTH the original and transpiled paths and instrumenting if either does match would be more robust and less surprising.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions