Skip to content

Refactoring for "proper" structure #1082

@mbabker

Description

@mbabker

The way we wrote Framework apps in 2013/2014 very loosely modeled the architecture of the CMS as far as practices went. And it shows in how there are a bunch of global static accessors and the DI container is misused as a service locator.

Let's get serious here. It's time to refactor for best practices and to implement a proper application structure.

Along the way, everything needs to have automated testing put behind it (use the test framework for the stats API app as an example of how basically everything can be covered in some way).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions