Issue 7076 - Fix relative paths for nodes - #7095
Closed
CarycaKatarzyna wants to merge 1 commit into
Closed
Conversation
Member
|
Thanks @CarycaKatarzyna!
I'm not sure that is correct: the @RonnyPfannschmidt can you please correct me if I'm wrong? |
Member
|
this absolutely has to use rootdir, we cant use invocationdir as things are now |
Member
|
Right thanks. @CarycaKatarzyna thanks again for the PR, but we will need to decline this as is. Feel free to open another PR if you come up with a different approach! 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It solves #7076. I decided to change
rootdirtoinvocation dirin_bestrelpathcache, because we want to have path for nodes relative to invocation directory. As I've seen, that function is used only for nodes (_node_location_to_relpath), so this change shouldn't mess other functionalities.