Curated collection of useful Angular snippets that you can understand in 30 seconds or less.
- Use Ctrl + F or command + F to search for a snippet.
- Snippets are written in Angular 7.2.8+.
Beginner snippets
Intermediate snippets
- Adding keyboard shortcuts to elements
- Bind to host properties with host binding
- Global event listeners
- Injecting document
- Style bindings
- Window Location injection
Advanced snippets
Enums are great but they are not visible in Angular templates by default. With this little trick you can make them accessible.
enum Animals {
DOG,
CAT,
DOLPHIN
}
@Component({
...
})
export class AppComponent {
animalsEnum: typeof Animals = Animals;
}
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: enums,templates
If you're using ViewEncapsulation
value which is different than default, it might be daunting to set the value manually for every component.
Luckily you can configure it globally when bootstrapping your app:
platformBrowserDynamic().bootstrapModule(AppModule, [
{
// NOTE: Use ViewEncapsulation.None only if you know what you're doing.
defaultEncapsulation: ViewEncapsulation.None
}
]);
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: configuration,styling
To avoid the expensive operations, we can help Angular to track which items added or removed i.e. customize the default tracking algorithm by providing a trackBy option to NgForOf.
So you can provide your custom trackBy function that will return unique identifier for each iterated item. For example, some key value of the item. If this key value matches the previous one, then Angular won't detect changes.
trackBy takes a function that has index and item args.
@Component({
selector: 'my-app',
template: `<ul>
<li *ngFor="let item of items; trackBy: trackByFn">{{item.id}}</li>
</ul>`,
})
export class AppComponent {
trackByFn(index, item) {
return item.id;
}
}
If trackBy is given, Angular tracks changes by the return value of the function.
Now when you change the collection, Angular can track which items have been added or removed according to the unique identifier and create/destroy only changed items.
https://angular.io/api/common/NgForOf https://angular.io/api/core/TrackByFunction
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: good-to-know,tips,components,performance
It's really easy to add keyboard shortcuts in the template:
<textarea (keydown.ctrl.enter)="doSomething()"></textarea>
Bonus
<input (keydown.enter)="...">
<input (keydown.a)="...">
<input (keydown.esc)="...">
<input (keydown.shift.esc)="...">
<input (keydown.control)="...">
<input (keydown.alt)="...">
<input (keydown.meta)="...">
<input (keydown.9)="...">
<input (keydown.tab)="...">
<input (keydown.backspace)="...">
<input (keydown.arrowup)="...">
<input (keydown.shift.arrowdown)="...">
<input (keydown.shift.control.z)="...">
<input (keydown.f4)="...">
https://alligator.io/angular/binding-keyup-keydown-events
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: tips,good-to-know
Every rendered angular component is wrapped in a host element (which is the same as component's selector).
It is possible to bind properties and attributes of host element using @HostBinding decorators, e.g.
import { Component, HostBinding } from '@angular/core';
@Component({
selector: 'my-app',
template: `
<div>Use the input below to select host background-color:</div>
<input type="color" [(ngModel)]="color">
`,
styles:[`:host { display: block; height: 100px; }`]
},
)
export class AppComponent {
@HostBinding('style.background') color = '#ff9900';
}
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: components
It is possible to add global event listeners in your Components/Directives with HostListener
. Angular will take care of unsubscribing once your directive is destroyed.
@Directive({
selector: '[rightClicker]'
})
export class ShortcutsDirective {
@HostListener('window:keydown.ArrowRight')
doImportantThings() {
console.log('You pressed right');
}
Bonus
You can have multiple bindings:
@HostListener('window:keydown.ArrowRight')
@HostListener('window:keydown.PageDown')
next() {
console.log('Next')
}
You can also pass params:
@HostListener('window:keydown.ArrowRight', '$event.target')
next(target) {
console.log('Pressed right on this element: ' target)
}
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: events,components
Sometimes you need to get access to global document
.
To simplify unit-testing, Angular provides it through dependency injection:
import { DOCUMENT } from '@angular/common';
import { Inject } from '@angular/core';
@Component({
selector: 'my-app',
template: `<h1>Edit me </h1>`
})
export class AppComponent {
constructor(@Inject(DOCUMENT) private document: Document) {
// Word with document.location, or other things here....
}
}
https://angular.io/api/common/DOCUMENT
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: dependency injection
You can use advanced property bindings to set specific style values based on component property values:
<p [style.background-color]="'green'">
I am in green background
</p>
<p [style.font-size.px]="isImportant ? '30' : '16'">
May be important text.
</p>
Bonus
<!-- Width in pixels -->
<div [style.width.px]="pxWidth"></div>
<!-- Font size in percentage relative to the parent -->
<div [style.font-size.%]="percentageSize">...</div>
<!-- Height relative to the viewport height -->
<div [style.height.vh]="vwHeight"></div>
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: styles
For testing purposes you might want to inject window.location
object in your component.
You can achieve this with custom InjectionToken
mechanism provided by Angular.
export const LOCATION_TOKEN = new InjectionToken<Location>('Window location object');
@NgModule({
providers: [
{ provide: LOCATION_TOKEN, useValue: window.location }
]
})
export class SharedModule {}
//...
@Component({
})
export class AppComponent {
constructor(
@Inject(LOCATION_TOKEN) public location: Location
) {}
}
https://itnext.io/testing-browser-window-location-in-angular-application-e4e8388508ff https://angular.io/guide/dependency-injection
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: dependency-injection,testing
It's possible to use @ViewChild
(also @ViewChildren
and @ContentChild/Children
) to query for components of different types using dependency injection.
In the example below we can use @ViewChildren(Base)
to get instances of Foo
and Bar
.
abstract class Base {}
@Component({
selector: 'foo',
providers: [{ provide: Base, useExisting: Foo }]
})
class Foo extends Base {}
@Component({
selector: 'bar',
providers: [{ provide: Base, useExisting: Bar }]
})
class Bar extends Base {}
// Now we can require both types of components using Base.
@Component({ template: `<foo></foo><bar></bar>` })
class AppComponent {
@ViewChildren(Base) components: QueryList<Base>;
}
https://www.youtube.com/watch?v=PRRgo6F0cjs
⭐ Interactive demo of this snippet | ⬆ Back to top | tags: good-to-know,tips,components,dependency-injection