Expand FileRoot to its exec path in command lines
#28074
+132
−53
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.
Before this commit,
FileRootobjects were stringified to their absolute (!) path with aderived/sourcesuffix, which is neither hermetic nor useful.In the future, when path mapping is restricted to path stripping, which can be applied to prefixes of full exec paths without knowing the full path,
FileRootobjects can be path mapped automatically. Even before that happens, allowing users to e.g. doargs.add(ctx.bin_dir)avoids a gotcha and makes it easier to write code that can be path mapped in the future.Along the way improve test coverage by parametrizing tests in the choice of
NestedSetvs. list.