March 8, 2019
11:33 a.m.
Iâm sure we have something in the image that deals with this - but if writing a generic http retriever and wanting to correctly cope with constructing resource paths where the base path may or may not have a trailing /, and the resource path may or may not have a leading / Basically - magically handle /name//resourse /name///resource Iâm sure we have something simple - the best I could see was to abuse Path like: (Path from: basePath, '/', resourcePath) pathString Is this a good way to do it? Tim