Support module?

[thearabbit]

I would like to create 2 module in my app.

loan/
-----Collection
-----Template
saving/
-----Collection
-----Template

Support module or not?

[idmontie]

I have been thinking about it since any folder named client (anywhere in your app) will not be loaded by the server and vice versa.

Good point. 👍.

[idmontie]

I was thinking about this and there is not always a 1 to 1 (or even a many to 1) relationship between views and a collection. For example, in an app I recently wrote, the collection feeds data into many different types of views, but those views might also listen to different data.

I like the idea of the module pattern, but I think the line needs to be drawn at making modules centered around components:

MyComponent
├── MyComponent-spec.js (Test the Component)
├── MyComponent.jsx
├── MyComponent.md (Documentation on the component)
└── _MyComponent.scss (Style the Component)

To put anything else in there suggests to me that it would belong SOLELY to that component or be tied to only that view; but, in reality, I don't think I've written many collections that were uses solely by one component.

Thoughts on this would be appreciated, I am open for discussion and this is not set in stone.

[thearabbit]

Thanks for your reply, I use to use Laravel-PHP, it support module call workbench (look great).
Very happy, SpaceKitty !!!