Skip to content
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.

Avoid reporting ranges in the wrong files. #44

Open
vinivendra opened this issue Jun 6, 2020 · 0 comments
Open

Avoid reporting ranges in the wrong files. #44

vinivendra opened this issue Jun 6, 2020 · 0 comments
Labels
bug Something isn't working no solution yet It is not yet clear how to solve this issue

Comments

@vinivendra
Copy link
Owner

Currently, source file ranges only include information on the lines and columns of a file, but not on the file path. The code assumes the range is relative to the current file being translated, which is almost always the case, but can cause issues when an expression comes from another file (for instance the templates library).

If the file path was included in the range, this could be fixed, but it might cause performance issues.

@vinivendra vinivendra added bug Something isn't working no solution yet It is not yet clear how to solve this issue labels Jun 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working no solution yet It is not yet clear how to solve this issue
Projects
None yet
Development

No branches or pull requests

1 participant