In our Project we used the "Config-Scope Path Browser", with the parameter "appendPath" which was perfect for referencing the Path Scope relative to the site root Path.
But this component is marked as "deprecated", so I don't want to depend on this any more.
I now use the "wcm-io/handler/url/components/granite/form/siteRootPathBrowser" with an predicate which filters the unwanted path. But this is not ideal there is too much to click and unwanted info on the first levels, which have only one selection possible on the level.
It would be great to integrate the "appendPath" Property from the deprecated "Config-Scope Path Browser" into the "PathField" and "PathBrowser" Component in the URL Handler.
this is a good idea, we'll add appendPath support for the other pathfield/browser components as well.
support for "appendPath" properties in all pathfield-/pathbrowser-derived GraniteUI components is added in the next versions of URL Handler, Link Handler and Media Handler.
as dependency it's also required to update the io.wcm.wcm.ui.granite bundle as it's the common base for all pathfield widgets.