Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Support relative paths in interceptors #71879
Support relative paths in interceptors #71879
Changes from 11 commits
26fe473
92927a8
81a7a60
462ff45
805bb13
b7eafa7
7d11582
714b2df
b40ad6c
9f2c0c0
826168f
cd0d5a7
3681998
f59f20a
aa52b66
b18f5a2
9dab4fa
82dc78a
551cfc1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't this be summarized as
If not in what ways are they different?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The doc still says that we consider mapped path here, thought we decided it would just match
#line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The term mapped path is used in reference to
/pathmap
, not#line
mapping. This sentence is meant to say that presence or absence of#line
in source code doesn't affect what anInterceptsLocationAttribute
means (aside from the trailing newline affecting the line numbers of the subsequent lines).I think this is something which will become much simpler conceptually as we phase out the "compat" lookup. Basically, there will no longer be any expectation for the user of
[InterceptsLocation]
to perform any kind of mapping of the file path, line, or column; rather, to just get and use a relative path from the "current file" to the "referenced file", and to use the "unmapped" line and column numbers.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Point (2) still says that path map impacts how we resolve paths in
InterceptsLocation
. That means the following paths do not necessarily mean the same thing.That feels very broken. Both of these features are about mapping a file path, relative or absolute, to another file in the compilation. Why should one use
/pathmap
and the other not use it?If I'm incorrect and
#line
does respect path map for embedding I'm happy to be corrected on this point. If it does though why do we have such a complex section on how this mapping works. Why can't we just simply say: