@Abdizriel, a while ago, when the generator started, the idea was to have options for the the user (#15), so he'd choose between a "flat" achitecture, which is what we didn't implement at first, and the "deep" architecture which is what we currently have as default.

The major point against the "flat" one was about the bigger projects, because depending on how the user created/separated his folders, there would be a lot of different files to be taken care of - which is a mess. For example, say the name of the parent folder is "medic", if the user puts the components, templates, styles, services, parsers, models, etc; all in there, we'd a big mess to take care of - even though they're all about medic.

And that was solved by the "deep" one, which introduces more context to what "medic" might have.

As for the tests, this issue #60 is still open. Since it's not as much needed (even though I'd love to have it), I've been pretty much passing it from version to version - it might land after the 1.10, though.

Maybe you could add another issue with the suggestion so we can track and implement it? I'll gladly target it to 1.11.

App Structure #168

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions