Skip to content

Refactorize the project structure #19

@pvk-developer

Description

@pvk-developer

The project structure at the moment looks like this:

├── action.py
├── actions
│   ├── hello.py
│   └── __init__.py
├── api.py
├── application.py
├── cli.py
├── __init__.py
├── logging_utils.py
├── middleware.py
├── resource.py
├── resources
│   ├── __init__.py
│   └── misc.py
├── runnable.py
└── utils.py

The file action.py and resource.py both contain the BaseAction and BaseResource which are supposed to be inherit from.

I would like to suggest to change action.py and resource.py into base.py inside the folders actions and resources. Also, the cli.py we should rename it to __main__.py to follow the new standards.

.
├── actions
│   ├── base.py
│   ├── hello.py
│   └── __init__.py
├── api.py
├── application.py
├── __init__.py
├── logging_utils.py
├── __main__.py
├── middleware.py
├── resources
│   ├── base.py
│   ├── __init__.py
│   └── misc.py
├── runnable.py
└── utils.py

Also, here I'm open for suggestions, the utils.py file and logging_utils.py can create a module named utils or be unified in the same file ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions