Used consistent absolute file paths.#20
Merged
olasitarska merged 1 commit intoDjangoGirls:masterfrom Jul 6, 2014
Merged
Conversation
When giving the name of a file for editing, the "absolute"
path is always used ("absolute" relative to the root of the project)
Member
|
I think this makes a lot of sense :) |
olasitarska
added a commit
that referenced
this pull request
Jul 6, 2014
Used consistent absolute file paths.
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
2 participants
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.
I noticed that file paths were inconsistent in that they would sometimes include the full
mysite/...and sometimes not.This PR fixes all paths to use the full version.
It makes it less ambiguous but it's also a bit more verbose so I'm not sure if it's an improvement.
What do you think?