3 ms·
> heavyweight I can agree with you there if by heavyweight you're referring to it's explicit definitions. However, have you tried a "SharedModule"? You can th
by TheSpiciestDev 7y ago
> heavyweight
I can agree with you there if by heavyweight you're referring to it's explicit definitions.
However, have you tried a "SharedModule"? You can throw any number of tiny components into however many shared modules (one shared module for your small-medium sized application vs n-number of lazily loaded shared modules for your large+ applications.)
I myself enjoy wrapping even helper components in modules because I then know exactly what a component needs and it's scope of dependencies.
- ousta 7y agoI agree. you need to think about where to put your component, when to design components containing components and when to design a global component embedding everything in one, when to create new services, what should be the service range, will ever components need that service or no, ect, and they are all hard choices to get back from once you have a big codebase