Web components solve the problem of different implementations of controls. The bottom line is: if you build solutions using more than one framework, reusing your work is complicated. In essence, they're all the same, but because they are so tightly coupled to the particular framework, they can't be reused in other frameworks. ![]() Vue has components too, which are almost like Angular but not quite the same and if you use jQuery, Knockout or Handlebars you need to solve the problem differently altogether. AngularJS has directives, React has components, Angular has components too, but they are totally different than React component. But while the concept is ubiquitous, the implementation isn't.Īs many JavaScript frameworks are there, as many definitions of what a control or a component is. Controls not only help you build a consistent UI but also help you prevent repeating yourself: build the functionality once and reuse as often as you need. It can be as simple as a button or as complex as a document card, interactive table or a data grid. ![]() Sometimes they're called controls, sometimes components, but the idea behind them is the same: build a reusable piece of UI that you can configure to match the exact needs. Probably every technology for building applications out there has the notion of reusable building blocks. But do they have a place in the SharePoint Framework and if so how to they fit together? Controls everywhere but not for everyone Web components are the holy grail of reusable controls.
0 Comments
Leave a Reply. |