stack build gives InvalidAbsDir

[dtaskoff]

I just updated to stack 1.2.0
and my stack build is failing with the following error:
option --extra-lib-dirs: InvalidAbsDir "/home/me/XX/YY/../ZZ/UU/VV/WW"

The command I'm running is
stack build --extra-lib-dirs="$lib"
where $lib is the path mentioned above.

Note: The same command ran successfully before the update.

Edit: Seems like it's failing because of the .., since given the same path without it works perfectly fine.

[mgsloan]

Not sure what we should do about this. I think this general issue affects everything that uses the functions like absDirOption / relDirOption / etc.

@chrisdone Maybe we should put FilePath in our config types? Seems like a cop-out! Or, relax the constraints of the path library? (dangerous semantics change, though!). Perhaps Path needs more types?

[chrisdone]

It's true that fundamentally a user's input is incomplete and we need IO to fill in the gaps. Ideally we'd resolve the user input into a normalised absolute directory, via resolveDir' from path-io. I don't know whether optparse-applicative is capable of running as a monad transformer like Web formlets, that would allow us to do the resolving before it gets into our configuration types.

What type would this be?

[mgsloan]

I'm not sure, how about LenientPath Dir ?

[dtaskoff]

Any updates on this?
The issue is still there, with the latest stack version - 1.3.0.

[dtaskoff]

Is there any progress on that issue? Still happening with 1.4.0.

Note: Won't using something like that function fix the issue easily?

[mgsloan]

Fixed in HEAD - see #2830