Skip to content

Code separation in Admin-CP-Files #134

@Lukas-Kullmann

Description

@Lukas-Kullmann

Now there are lots of files in the admin-cp-folder containing all kinds of actions (e.g. listing, deleting, editing (saving and displaying) of articles is in one file). For clarity-reasons these functions should be separated into multiple files.
Furthermore it would be nice if there was some kind of view-file so that logic and display of information is not mixed which would make the code more maintainable.
Of course it would be best if there was the possibility to store all the code for one topic (including frontend and backend code of news, articles, downloads, etc.) in one folder. So that you don't have to search for code all over the project. But changing this would really be a long-term-project.

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