(www.seangoedecke.com)

428 points ahamez | 1 comments | 24 Aug 25 19:10 UTC | HN request time: 0s | source

Show context

wener ◴[25 Aug 25 00:25 UTC] No.45009059[source]▶

I still try think /v1 /v2 is a break, I don't trust you will keep v1 forever, otherwise you'll never introduce this execuse.

I'd like to introduce more fields or flags to control the behavior as params, not asking user to change the whole base url for single new API.

replies(1): >>45009097 #

1. calrain ◴[25 Aug 25 00:32 UTC] No.45009097[source]▶

>>45009059 #

I like this pattern.

When an API commits to /v1 it doesn't mean it will deprecate /v1 when /v2 or /v3 come out, it just means we're committing to supporting older URI strategies and responses.

/v2 and /v3 give you that flexibility to improve without affecting existing customers.

↑

Everything I know about good API design