As I currently refactor an app to this structure I am missing native generator support (I can create components, but I have to move them and adjust the imports).
I would like to work on an update that during installation prompts the user to choose between the default app structure (the one we have right now) or a pod structure.
There are a few ways about implementation that I have in mind, but before going ahead I'd like to make sure this would be considered a feature worth merging.
As far as the user interface is concerned, I'd plan to have a new sub generator that creates (or deletes) new pods (e.g. yo react-webpack:pod blog), as well as extending the component subgen to support a --pod=<podname> option that would create new components and their tests at the right paths.
I borrowed the term from the Ember world, where this kind of structure was pretty common (at the time I was using it) and is supported by ember-cli:
So an app dir might look like this
As I currently refactor an app to this structure I am missing native generator support (I can create components, but I have to move them and adjust the imports).
I would like to work on an update that during installation prompts the user to choose between the default app structure (the one we have right now) or a pod structure.
There are a few ways about implementation that I have in mind, but before going ahead I'd like to make sure this would be considered a feature worth merging.
As far as the user interface is concerned, I'd plan to have a new sub generator that creates (or deletes) new pods (e.g.
yo react-webpack:pod blog
), as well as extending the component subgen to support a--pod=<podname>
option that would create new components and their tests at the right paths.