Repository navigation
Api version control #148
Description
What is the best approach to handle different api versions?
To create separate projects for each:
tapioca-myapi-v1
tapioca-myapi-v2
Or to use the same project but different major version that match the api version?
tapioca-myapi==1.0.0 # for v1
tapioca-myapi==2.0.0 # for v2
which one of these do you think is the best idea, or there is another way to do that?
Activity
[-]Api versions control[/-][+]Api version control[/+]filipeximenes commentedon Dec 13, 2017
Hey, I think the first approach (multiple packages) is cleaner and easier to maintain. That's how I've been doing things so far. Someone proposed a built in solution for the second approach long time ago, but we decided it was not worth. Just simpler to have multiple packages.