ForNeVeR/TruePath

`PathStrings.Normalize("../../foo")` is broken

Closed this issue · 0 comments

ForNeVeR commented

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:

    [InlineData("../../foo", "../../foo")]
    [InlineData("../../../foo", "../../../foo")]