Skip to content

[Back-end] Refactoring JDH Django API #323

@salaun-marion

Description

@salaun-marion

To do when we will have time

Maybe we should move to another type of 'architecture' for the back-end repository :

→ What we currently have :

└── jdhapi
            └──  ....
            └── migrations
            └── models
            └── serializers
            └── utils
            └── views
                       └── articles
                       └── abstracts
                       └── ...
            └── urls.py
            └── ...

→ What maybe we should do :

└── jdhapi
            └── ....
            └── articles
            └── abstracts
            └── issues
            └── callforpapers
            └── authors
                       └── url.py
                       └── model.py
                       └── serializers.py
                       └── ...
            └── ...

We can look at this example from the Real World Example Apps.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions