Skip to content

Models in POD structure #28

Closed
Closed
@ryan0x44

Description

@rjackson

The new POD structure (#16) is working really well, however the directory structure becomes a little messy with models, as we use the singular name for models and the plural name for controllers/routes.

For example, say we have a post entity, the pod structure would be:

  • pods
    • post
      • model.js
    • posts
      • controller.js
      • route.js

But this would be neater:

  • pods
    • posts
      • model.js
      • controller.js
      • route.js

Of course one way to achieve this is to override the resolveModel method and account for use of the plural, which I'm currently investigating as a solution.

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