Hi there, The rise of TypeScript, closure compiler and facebook flow highlights that even javascript developers sometimes miss static type checking. I'm wondering if Angular developers miss type safety in their templates. I've sumed up my point of view in this blogpost: https://medium.com/doctusoft-coding-style/benefits-of-imperative-type-safe-views-d9ca4707a48a To outline, I think creating views in an imperative way can have big benefits over html templating:
- template hierarchy is *discoverable, navigable*, easire to refactor. - binding expressions can be *typesafe *and compile-time checked. What do you thing? Does anyone else miss these things? I've already prototyped doing this with angular 1.x, but I'm wondering if we can have first-class support to imperatively build views in major frameworks. Cheers, Gábor -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
