ThomasBurleson

export interface ResponseError = [any, Error];	// Tuple to return either 

/**
 * special promise trap to build tuple of reponse and error
 */
const trap = (promise): Promise<ResponseError> => {  
  return promise
    .then(data => ([data, undefined]))

ThomasBurleson

Flawed Commit Strategy

Developers often want to condense their git log output. However without a proper git commit strategy (and conventions), those condensed outputs are still flawed.

For details on condensed git log outputs, see Improve your Git Log Output

Consider a git lg output for a typical project:

ThomasBurleson

Quite simply, because Observables can encapsulate many different types of sources and those sources don't necessarily have to obey that interface. Some like Promises always attempt to eagerly compete.

Consider:

const promise = $.get('https://www.google.com');

ThomasBurleson

<!-- wInViewRoot directive is needed to specify the `root` for `IntersectionObserver` and some other it's options e.g. `margin` -->
<div class="container" wInViewRoot="viewport">
  Any content can be here
  <w-in-view-item>
    <!-- Content will be replaced by a placeholder <div> with the same height as original content.
         Also `InViewItemComponent`s change detector will be detached when it become invisible which means
         all the content's change detectors won't be reachable and will be inactive as well. -->   
  </w-in-view-item>
  ...or any other content can be here
  <w-in-view-item>

ThomasBurleson

/**
 *
 * Snippet from blog article:  https://auth0.com/blog/ngrx-facades-pros-and-cons/
 *
 */

@Component({
  selector: 'abl-books-page',
  changeDetection: ChangeDetectionStrategy.OnPush,
  template: `

ThomasBurleson

export function log(task: string) {
 const announceCompleted = () =>  {
    console.log(`${task} %ccomplete`, 'color: green');
 };
 return function<T>(source: Observable<T>) {
   return source.pipe(
     tap(
      console.log, 
      console.error, 
      announceCompleted 

ThomasBurleson

import {
  Component,
  OnInit,
  Input,
  ViewChild,
  ElementRef,
  HostBinding
} from '@angular/core';

@Component({

ThomasBurleson

import { NgModule } from '@angular/core';
import { TestBed } from '@angular/core/testing';
import { readFirst } from '@nrwl/nx/testing';

import { EffectsModule } from '@ngrx/effects';
import { StoreModule, Store } from '@ngrx/store';

import { NxModule } from '@nrwl/nx';

/**

ThomasBurleson

Scenario

We want to build a custom schematic for company Aero that will internally do two things:

• build a new ngrx library using Nx workspace naming conventions
• generate ngrx state-management files; include the *.facade.* files

---

Important: This example is valid ONLY for Nx v6.2.x or higher!

ThomasBurleson