Skip to content

reconsider code organization #11

Description

@cameron

Currently, you've got a controllers.js file that housed almost all of your logic, including data access. For such a simple app, this is mostly okay, but as apps scale, this kind of organization will fail quickly. Consider organizing code by feature (e.g., conversation, profile) instead of by code artifact type (e.g., controller, template, service).

Here's a concrete example

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