What is the problem this feature would solve?
HttpClientRequest.appendUrl just appends whatever string you give to it at the end of the current client base URL. I think it should instead follow the same mechanism as new URL(path,base)
Here you have a reproduction where you see how it behaves: https://effect.website/play#3b8b4bfe0a61
What is the feature you are proposing to solve the problem?
Use proper url concatenation mechanisms, the equivalent of doing new URL(newPath,existingUrlInContext)
What alternatives have you considered?
for now, just being careful, or not using appendUrl