This raises a lot of questions in my mind. How dependency to angular is going to be managed? Hiw they are going to be packaged? Is there any restrictions on compilation mode (JIT/AOT)? More importantly, how this stuff work? What is the api for creating web components (or should I say angular elements) out of angular components?
How do you drive web component when It depend to another library ? Currently I'm doing web component for example with angular material and I build component with Dialog and I encapsulated that with ShadowDom, but.... when I want to use this component en other aplication angular de Dialog modal dont work. Do you have any idea about problem ?
Should have been a feature since day one, but happy that its going somewhere... hopefully one day we will have true web components, not XYZ framework components... also if this goes forward polymer RIP!
Aun que creo que ya es tiempo. De implementar un cms como joomla o WordPress. A angular Ya que han pasado varios años y es un buen modelo de negocios. Es decir: Es mas notable y mas estable. Saludos desde Cúcuta. N.S
Why bother with the Angular-isms when you can just create a native component? Yes, there is a bit of boiler plate, but most of that can be handled by libraries and they don't fatten the code. You can use a native component anywhere and no need to require Angular, React or anything else. And these components can be used in any framework as he demoed. But to force me to use Angular to create something natively supported seems like a waste of memory and forces me to learn how to write a component in the Angular way instead of a truly 100% cross-framework-compatible way (Native).
Basically, it means existing angular components converted or exposed as web components. And also allows you to create web components with angular, which is less cumbersome than native if you already know how.
This is a new era opening for Angular! The use cases are almost infinite. Great !
Yep, I need this in my life.
Very exciting--as Rob said, particularly for enterprises with mixed tech stacks.
I need this ASAP!!!
Cooool! Why on earth those audience are just staring at him! 👏👏👏
This raises a lot of questions in my mind. How dependency to angular is going to be managed? Hiw they are going to be packaged? Is there any restrictions on compilation mode (JIT/AOT)?
More importantly, how this stuff work? What is the api for creating web components (or should I say angular elements) out of angular components?
Yea good point.
How do you drive web component when It depend to another library ? Currently I'm doing web component for example with angular material and I build component with Dialog and I encapsulated that with ShadowDom, but.... when I want to use this component en other aplication angular de Dialog modal dont work. Do you have any idea about problem ?
AWESOME!!!
This is amazing
how to implement custom property pane in spfx with angular component
awesome!
Genial ❤
Will be a great solution for using the SharePoint Framework with Angular
WOW!!!
Wow pretty cool...
Should have been a feature since day one, but happy that its going somewhere... hopefully one day we will have true web components, not XYZ framework components... also if this goes forward polymer RIP!
It's about time that angular (or react) should realize that the platform provides most of what it takes in delivering custom components.
Aun que creo que ya es tiempo. De implementar un cms como joomla o WordPress. A angular
Ya que han pasado varios años y es un buen modelo de negocios. Es decir: Es mas notable y mas estable.
Saludos desde Cúcuta. N.S
Why bother with the Angular-isms when you can just create a native component? Yes, there is a bit of boiler plate, but most of that can be handled by libraries and they don't fatten the code. You can use a native component anywhere and no need to require Angular, React or anything else. And these components can be used in any framework as he demoed. But to force me to use Angular to create something natively supported seems like a waste of memory and forces me to learn how to write a component in the Angular way instead of a truly 100% cross-framework-compatible way (Native).
Basically, it means existing angular components converted or exposed as web components. And also allows you to create web components with angular, which is less cumbersome than native if you already know how.