Re: Structuring an API in a large project

2014-05-02 Thread Adam "Cezar" Jenkins
On Fri, May 2, 2014 at 10:44 AM, Scot Hacker wrote: > On Thursday, May 1, 2014 8:59:25 AM UTC-7, Cezar Jenkins wrote: >> >> >> As you can guess, the views.py file is pretty big and I want to refactor >> this out. Currently I have a few options in front of me, the one I'm >> leaning towards is to

Re: Structuring an API in a large project

2014-05-02 Thread Scot Hacker
On Thursday, May 1, 2014 8:59:25 AM UTC-7, Cezar Jenkins wrote: > > > As you can guess, the views.py file is pretty big and I want to refactor > this out. Currently I have a few options in front of me, the one I'm > leaning towards is to put an 'api/v1' package into each app and use the api > ap

Re: Structuring an API in a large project

2014-05-02 Thread Adam "Cezar" Jenkins
On Thu, May 1, 2014 at 8:15 PM, Mike Dewhirst wrote: > On 2/05/2014 10:29 AM, Adam "Cezar" Jenkins wrote: > >> >> >> >> On Thu, May 1, 2014 at 5:36 PM, Mike Dewhirst > > wrote: >> >> On 2/05/2014 2:16 AM, Adam "Cezar" Jenkins wrote: >> >> On Thu, May 1, 2

Re: Structuring an API in a large project

2014-05-01 Thread Mike Dewhirst
On 2/05/2014 10:29 AM, Adam "Cezar" Jenkins wrote: On Thu, May 1, 2014 at 5:36 PM, Mike Dewhirst mailto:mi...@dewhirst.com.au>> wrote: On 2/05/2014 2:16 AM, Adam "Cezar" Jenkins wrote: On Thu, May 1, 2014 at 11:10 AM, Venkatraman S mailto:venka...@gmail.com>

Re: Structuring an API in a large project

2014-05-01 Thread Adam "Cezar" Jenkins
On Thu, May 1, 2014 at 5:36 PM, Mike Dewhirst wrote: > On 2/05/2014 2:16 AM, Adam "Cezar" Jenkins wrote: > >> On Thu, May 1, 2014 at 11:10 AM, Venkatraman S > > wrote: >> >> >> >> On Thu, May 1, 2014 at 9:29 PM, Cezar Jenkins >> mailto:emperorce...@gmail.com>> w

Re: Structuring an API in a large project

2014-05-01 Thread Mike Dewhirst
On 2/05/2014 2:16 AM, Adam "Cezar" Jenkins wrote: On Thu, May 1, 2014 at 11:10 AM, Venkatraman S mailto:venka...@gmail.com>> wrote: On Thu, May 1, 2014 at 9:29 PM, Cezar Jenkins mailto:emperorce...@gmail.com>> wrote: Right now I have a large project with an equally large API (

Re: Structuring an API in a large project

2014-05-01 Thread Venkatraman S
On Thu, May 1, 2014 at 9:46 PM, Adam "Cezar" Jenkins wrote: > On Thu, May 1, 2014 at 11:10 AM, Venkatraman S wrote: > >> >> >> On Thu, May 1, 2014 at 9:29 PM, Cezar Jenkins wrote: >> >>> Right now I have a large project with an equally large API (done using >>> django rest framework). The curren

Re: Structuring an API in a large project

2014-05-01 Thread Adam "Cezar" Jenkins
On Thu, May 1, 2014 at 11:10 AM, Venkatraman S wrote: > > > On Thu, May 1, 2014 at 9:29 PM, Cezar Jenkins wrote: > >> Right now I have a large project with an equally large API (done using >> django rest framework). The current structure is something like this: >> >> api >> |-urls.py >> |

Re: Structuring an API in a large project

2014-05-01 Thread Venkatraman S
On Thu, May 1, 2014 at 9:29 PM, Cezar Jenkins wrote: > Right now I have a large project with an equally large API (done using > django rest framework). The current structure is something like this: > > api > |-urls.py > |-models.py > | > v1 > |-views.py > |-serializers.

Structuring an API in a large project

2014-05-01 Thread Cezar Jenkins
Right now I have a large project with an equally large API (done using django rest framework). The current structure is something like this: api |-urls.py |-models.py | v1 |-views.py |-serializers.py |-permissions.py |-tests.py etc As you can guess, t