Post

Developers who add the trailing slash to the base URL for API calls are evil. I can't be the only one who thinks that this is the only way. ❌ `${baseUrl}users ✅ `${baseUrl}/users`

20/11/24, 8:57 am1 repost9 likes

Nestor Vera

straight to jail tbh

Literally came across this exact issue today when migrating someone else’s code 😅

Chris Kalmar ⚡️ Chief Agent Director 😜

@chriskalmar.dev

20 Nov 2024

Yup, this makes it not very readable. Isn’t there a URL normalisation function like for paths, to overcome this?

Marc Backes

@marc.ba

21 Nov 2024

url.replaceAll(‘//‘, ‘/‘) 😂

Chris Kalmar ⚡️ Chief Agent Director 😜

@chriskalmar.dev

21 Nov 2024

I have a very very simple and super readable fix: [ url.split("://")[0], url .split("://")[1] .split("/") .filter((val) => val !== "") .join("/"), ].join("://") I'm playing with the idea of publishing a new NPM package 🤣

Alex Dixon

@dixonary.co.uk

20 Nov 2024

Unfortunately not - it's valid for http paths to have empty segments, and web servers may choose to treat example.com/a//b differently to example.com/a/b . But most don't bother and will quietly normalise.