Repository navigation
Multiple versions architecture #2131
Answered
by
karolzlot
adammrozik
asked this question in
Questions
|
Hey, I have a general architecture question. I see in your example that you hide all endpoints behind Second question is about other dependencies inside the package. What if there is some common code that is only used by v1? Do I just keep increasing common functionalities to enable all versions, or do I just hide the version specific code inside each of the version folders? |
Answered by
karolzlot
Aug 3, 2021
Replies: 1 comment
|
Changing api version is not something you would need to do often. To keep things simple I suggest to just use v1 version of api until you will have reason to have v2 which won't be backward compatible. (If v2 will be backward compatible, then maybe you don't need v2). |
0 replies
Answer selected by
tiangolo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Changing api version is not something you would need to do often. To keep things simple I suggest to just use v1 version of api until you will have reason to have v2 which won't be backward compatible. (If v2 will be backward compatible, then maybe you don't need v2).