Hi Bertrand Thanks for the explanation and finding a better name. I understand the concept now, but cannot think of a more intuitive name either. I guess it's just a case of people having to read the docs or examples and remember that it's called atParent().
Regards Julian On Mon, Dec 14, 2015 at 2:28 PM, Bertrand Delacretaz <[email protected]> wrote: > Hi, > > On Fri, Dec 11, 2015 at 5:13 PM, Bertrand Delacretaz > <[email protected]> wrote: >>... >> .resource("a/b").resetParent().resource("c/d") >> results in both /tmp/a/b and /tmp/c/d resources. ... > > I have renamed resetParent() to atParent() which should be more > intuitive, so that's now > > ResourceResolver r = ... > build.forResolver(r).resource("a/b").atParent().resource("c/d") > > to create both /a/b and /c/d, meaning "create c/d at the parent level". > > -Bertrand
