angular2-directives

I have used a custom directive to detect click outside an element in angular 2 but the same is not possible in angular 4. [plunkr] https://plnkr.co/edit/aKcZVQ?p=info When I try using the same code in angular-4 I get the following errors: 1. Argument of type '{ template: string; directives: typeof ClickOutside[]; }' is not assignable to parameter of type 'Component'. ==> @Component({ templateUrl: "", directives: [ClickOutside] }) 2. Type 'Subscription' is not assignable to type 'Observable<MouseEvent>'. in the directive inside ngOnInit() and ngOnDestroy() ngOnInit() { this.globalClick =

I'm new at Angular and I'm still trying to understand it. I've followed the course on the Microsoft Virtual Academy and it was great, but I found a little discrepancy between what they said and how my code behave! Specifically, I've tried to "put a component inside another component" like this: @Component({ selector: 'parent', directives: [ChildComponent], template: ` <h1>Parent Component</h1> <child></child> ` }) export class ParentComponent{} @Component({ selector: 'child', template: ` <h4>Child Component</h4> ` }) export class ChildComponent{} This is the same example that they make on the

I have an odd requirement and was hoping for some help. I need to focus on the first found invalid input of a form after clicking a button (not submit). The form is rather large, and so the screen needs to scroll to the first invalid input. This AngularJS answer would be what I would need, but didn't know if a directive like this would be the way to go in Angular 2: Set focus on first invalid input in AngularJs form What would be the Angular 2 way to do this? Thanks for all the help! This works for me. Not the most elegant solution, but given the constraints in Angular we are all experiencing

In Angular 1 we could make a directive attribute required. How do we do that in Angular 2 with @Input? The docs don't mention it. Eg. Component({ selector: 'my-dir', template: '<div></div>' }) export class MyComponent { @Input() a:number; // Make this a required attribute. Throw an exception if it doesnt exist @Input() b:number; constructor(){ } } Günter Zöchbauer Check in ngOnInit() (inputs aren't yet set when the constructor is executed) whether the attribute has a value. Component({ selector: 'my-dir', template: '<div></div>' }) export class MyComponent implements OnInit, OnChanges { @Input

I am having trouble finding a good autocomplete component for Angular2. Just anything that I can pass a list of key-label objects to and have a nice autocomplete on an input field. Kendo does not support Angular 2 yet and that it what we mostly use internally. It doesn't appear that Angular Material supports Angular 2 yet either. Can anyone please point me in the right direction or let me know what they are using? This is what I built so far. It's pretty bad and I'd like to find something that looks nice. import {Component, EventEmitter, Input, Output} from 'angular2/core'; import {Control}

I am trying to load a component dynamically from a parent component. While loading the child component I need to pass some input parameter as well. But I am getting the following error in the browser console. Error: Uncaught (in promise): TypeError: Cannot read property 'createComponent' of undefined at resolvePromise (zone.js:538) at zone.js:574 at ZoneDelegate.invokeTask (zone.js:356) at Object.onInvokeTask (lib/@angular/core/bundles/core.umd.js:9091) at ZoneDelegate.invokeTask (zone.js:355) at Zone.runTask (zone.js:256) at drainMicroTaskQueue (zone.js:474) at XMLHttpRequest.ZoneTask.invoke

I have an issue similar to Reset ngModel values on ngIf in angular2 I would like to set any ngModel values to null whenever a parent *ngIf causes that element to be hidden. I wouldn't be asking this if my situation was simple. If that were the case, then I'd just reset on the change of the *ngIf value, but since my form has multiple levels of *ngIf nesting and multiple *ngIfs can cause some elements to show/hide, I'd like to use some sort of directive to accomplish the resetting. I'd rather not have to convert all my simple input elements to components to take advantage of the OnDestroy event,