Should baseUrl be consistently implemented within the next, fetch and axios clients?

[franworks]

@mrlubos The baseUrl property in the axios and nuxt clients (baseURL) are different than the one in the next and fetch clients (baseUrl). When working with the axios client, baseURL as an option seemed like a mistake.

Should this configuration be updated to one or the other for consistency?

[mrlubos]

Definitely can't change Nuxt and Axios. You could make the argument for changing Fetch/Next.js/Angular to baseURL. I'm not sure it matters much? Since we build on top of frameworks, if there was a future client that named this value baseUrl, we would want to respect its naming and we'd be having this conversation again. What are you hoping to gain by making this naming consistent?

[franworks]

consistency across implementations of the Client Options interface is really it.

As I mentioned, I thought it was a mistake, seeing it in this codebase - even though I've used axios for years.

It's not a big deal, but I thought I'd raise the question to get your take on it.