Extend Documentation for using custom paths

[funkybaboon]

No description provided.

[HazAT]

Thx man! 🍺

[arekolek]

Note that you have to use a / in the beginning of the custom path, even if you're not starting from the root path

Why would you do such a thing? Wouldn't it be better for the path specifications to work like in every other tool that exists out there?

[ls-1N]

@arekolek Stupid things happen sometimes. This has been noticed multiple times and a fix is very easy, but it would break many existing setups. The underlying problem here is the avoidance of breaking changes even for major versions in the fastlane ecosystem. But I'm not qualified enough to decide what is best here. Just seems worrisome to have to memorize all the small unintuitive oddities.

I also took my time to report this issue (and searching existing issues and landing here) after having spent time figuring out why paths fail only to find out in the end that this is wontfix
:(