Discussion for angular (2+) - need help? create a stackblitz with your issue to get help faster using this template: https://stackblitz.com/fork/angular-issue-repro2
input
fields which stores a name and a number separately. The problem is I don't know how many pairs are needed; and the number of such pairs needed depends on a user input, e.g. if user enters 7, then I will need to dynamically generate 7 such pairs. Can someone please point how to handle this for a beginner like me? Any reference I can read?
@ObservableInput()
concentrates on transforming a standard input into an observable input, and as a result, simplification and standardization, how and where to detect a change on such input (usually used some code in ngOnChanges
or using setters, ...).
Hi,
I would like to lazy load the Vue runtime in Angular.
I have an ng app which might (or might not) load another app. This (second) app is based on Vue and expects the Vue runtime to be already available.
Vue seems to be available as a module: https://vuejsdevelopers.com/2019/02/04/vue-es-module-browser-build/
Is it possible to lazy load this with the import().then() approach?
Thanks!
Uncaught Error: Cannot find module '@angular/platform-browser'
at webpackMissingModule (main.js:11)
@danww You can do many things, including passing an observable with your logic and behavior, but
@ObservableInput()
concentrates on transforming a standard input into an observable input, and as a result, simplification and standardization, how and where to detect a change on such input (usually used some code inngOnChanges
or using setters, ...).
@mlc-mlapis Cool, that makes sense. I tend to work with a different pattern. I use ngrx, and usually have a per-feature container component, where I gather from the state, etc., all the data for the child components, and pass that data to the components as Observables or BehaviorSubjects. I use the OnPush ChangeDetection strategy in each Component, and so I never need/usengOnChanges
or getters/setters. It seems really simple and works really well, but I'm not sure if it's good/best practice.
| async
at the last possible opportunity in the template. Just thinking about it now, I wonder if there's a performance difference between passing Observables and plain objects into a Component?