We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
PathStrings.Normalize("../../foo")
PathStrings.Normalize is currently broken for certain non-normalized strings (starting from ..).
PathStrings.Normalize
..
It supports ../foo, but when it sees ../../, it thinks it should go one level up from ../ which is an empty path.
../foo
../../
../
So, an even number of .. gives an empty path, and an odd number of .. gives one ...
New broken tests:
[InlineData("../../foo", "../../foo")] [InlineData("../../../foo", "../../../foo")]
The text was updated successfully, but these errors were encountered:
(#60) PathStrings.Normalize: properly treat paths such as "../../foo"
f26f61c
(#60) Document the fix
4fd071d
ForNeVeR
Successfully merging a pull request may close this issue.
PathStrings.Normalize
is currently broken for certain non-normalized strings (starting from..
).It supports
../foo
, but when it sees../../
, it thinks it should go one level up from../
which is an empty path.So, an even number of
..
gives an empty path, and an odd number of..
gives one..
.New broken tests:
The text was updated successfully, but these errors were encountered: