I don't know whether you want to build just "paths" or valid URIs, if it's the latter, I'd suggest ZnUrl as well.

'/name/' asPath / 'resource'. -> /name/resource

'/name/' asPath / '/resource'. -> /resource (which is correct)

'/name/' asUrl / '/resource' -> /name//resource (which is correct as well).

The other way is to use path segments, as C��drick suggested.

Regards,

Esteban A. Maringolo

El vie., 8 mar. 2019 a las 8:34, Tim Mackinnon (<tim@testit.works>) escribi��:

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