Lars Gyrup Brink Nielsen LayZeeDK

Angular CLI version	Angular version	Node.js version	TypeScript version	RxJS version
~16.0.0	~16.0.0	^16.13.0 \|\| ^18.10.0	>=4.9.5 <5.1.0	^6.5.5 \|\| ^7.4.0
~15.2.0	~15.2.0	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	>=4.8.4 <5.0.0	^6.5.5 \|\| ^7.4.0
~15.1.0	~15.1.0	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	>=4.8.4 <5.0.0	^6.5.5 \|\| ^7.4.0
~15.0.5	~15.0.4	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	~4.8.4	^6.5.5 \|\| ^7.4.0
~14.3.0	~14.3.0	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.9.0	^6.5.5 \|\| ^7.4.0
~14.2.0	~14.2.0	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.9.0	^6.5.5 \|\| ^7.4.0
~14.1.3	~14.1.3	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.8.0	^6.5.5 \|\| ^7.4.0
~14.0.7	~14.0.7	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.8.0	^6.5.5 \|\| ^7.4.0
~13.3.0	~13.3.0	^12.20.2 \|\| ^14.15.0 \|\| ^16.10.0	>=4.4.4 <4.7.0	^6.5.5 \|\| ^7.4.0

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

Coding guidelines

This document is split into three sections

On General Code Health. This section contains guidelines intended encourage patterns which produce more maintainable, less bug prone, code.
On Angular Best Practices. This section outlines the practices related to Angular, Typescript, RxJs and @ngrx/store. Following these general coding guidelines will help make the application cleaner.
On Angular Performance. This section contains guidelines intended to make an Angular app trigger change detection less often and on less entities.

Docs

https://hackmd.io/@mhevery/BkDUxaW84/https%3A%2F%2Fhackmd.io%2Fc%2FBkDUxaW84%2Fedit%3Fedit?type=book

Issues

PRs/ Examples

https://github.com/angular/angular/pull/30533/files#diff-9d549aa403494fd043a146b8db64f503R264-R275

Reactive Angular Terminology

To have a common terminology I list some of the used terms here and explain their meaning and usage.

Used terms:

Asynchronous/Observable Primitive
Reactive Primitives
Primitive Reactive Problems
Bind
Connect

Enable `systemd` in WSL 2

**NOTE: If you have Windows 11 there is now an official way to do this in WSL 2, use it if possible - see MS post here (WINDOWS 11 ONLY)**

This guide will enable systemd to run as normal under WSL 2. This will enable services like microk8s, docker and many more to just work during a WSL session. Note: this was tested on Windows 10 Build 2004, running Ubuntu 20.04 LTS in WSL 2.

To enable systemd under WSL we require a tool called systemd-genie
Copy the contents of install-sg.sh to a new file /tmp/install-sg.sh:

flowchart TD
    A[ContentChild] --> B;
    B{Is static?} -- No --> C;
    B -- Yes --> D;
    C[Make the query<br>type optional] --> E(Access in<br>ngAfterContentInit<br>or later);
    D(Add assertion<br>in ngOnInit or<br>ngOnChanges) --> F;
    F[Add ! to<br>the query type] --> G(Access in<br>ngOnInit<br>or later)

	#! /bin/bash
	### BEGIN INIT INFO
	# Provides: dns-sync
	# Required-Start:
	# Required-Stop:
	# Default-Start: S
	# Default-Stop:
	# Short-Description: Synchronizes /etc/resolv.conf in WLS with Windows DNS - Matthias Brooks
	### END INIT INFO

	import { Injectable, Inject } from '@angular/core';
	import { ReplaySubject, Observable } from 'rxjs';
	import { DOCUMENT } from '@angular/common';

	@Injectable()
	export class LazyLoadingScriptService {
	_loadedLibraries: { [url: string]: ReplaySubject<any> } = {};

	constructor(@Inject(DOCUMENT) private readonly document: any) { }

	/**
	* @license
	* Copyright Google LLC All Rights Reserved.
	*
	* Use of this source code is governed by an MIT-style license that can be
	* found in the LICENSE file at https://angular.io/license
	*/

	// Here's an example of the before and after.
	// BEFORE