Hi all, We probably need a general review of the API to see if we have an overall consistency issue RE encoded vs decoded.
I prefer us to be considerate before adding APIs here and there. We could at least document what is expected for methods that return a String or consume a String. I wonder what the default expected behavior should be? Encoded URI Strings are more usable. Decoded String seem to make sense for pretty printing and display in UIs. WDYT? Gary On Wed, Apr 16, 2025, 10:22 Bernd Eckenfels <e...@zusammenkunft.net> wrote: > I did a larger VFS2 version jump and now have to deal with the aftermath, > This mostly involves fixing a few places which used getName().getPath() > into getPathDecoded(). However there is usage of > parent.getName().getRelativeName(f.getName()). When I look at the source it > does not decode the result, > > This is a bit unexpected (even ChatGPT thought it is decoded), so my > question, do we want to change this or should I add a > getRelativeNameDecoded() > analogous to getPathDecoded()? (The better name would be > getRelativePathDecoded but that would be hard to find since we already have > the wrongly names relativeName Variant. > > Gruß > Bernd > — > https://bernd.eckenfels.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
