@Emrvb wrote:
My primary worry is about how we're supposed to be working with components in templates. In my opinion templates should only be used to define where and how something is rendered. I always aim on shielding templaters/designers from as much logic as possible. To me it seems the way we are supposed to use components (e.g. as replacement to the itemController) causes too much business/program logic to bleed into the templates. I'm afraid that in the future even small changes in the logic will have more impact on the templates and templaters/designers need far more understanding of the program internals than desired.
I try to have my applications seem like magic to the templaters/designers in the same way Ember is magic to me as a developer. Follow convention and you have to do almost nothing and add X when you want something more specific. I feel like I'm losing this ability.
If my worries have not merit at all, feel free to comfort me with rationale. If they do have merit, I'd love to discuss how we could address this issue.
Posts: 1
Participants: 1