parsing: use relative paths; force absolute paths to relative #7579
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.
parsing.Context
now only expects the path to always be relative path. To clarify, it's relative if it's aLocalFileSystem
and relatively-absolute (relative to the root of the repo) in GitFileSystem, as opposed to being absolutely-absolute paths.This expectation for Context to always get a relative path is managed in
DataResolver
for now, as changing anything in higher level may not be trivial.This change, that it uses the relative path in
LocalFileSystem
and relatively-absolute paths inGitFileSystem
does affectdvc.params.diff()
. Before we were using same relative/absolute paths, which worked for both filesystems, but now we will receive the data in something like following format:So, as a result of this, this had to be transformed such that they return same paths, so that we can compare them easily.
Fix #7307.