Kamilnaja

//inside template
<label>Filtruj po rasie</label>
        <input type="text" name="filter" [(ngModel)]="term"/>
      </form>

      <div
        *ngFor="let dog of dogs | filter:term;
            let i = index"
            class="puppy-wrapper"
            (click)="onSelect(dog)"

gregarendse

Testing An Angular CLI Project in a Headless Environment

I recently started a new project and we used [Angular CLI][4] to get started. Angular CLI, as in the name, is a command line utility for creating and managing Angular 2 projects. Using Angular CLI to create a project is very easy and it gives you a great starting point for new Angular 2 projects. The only draw back I found was that in my mind it wasn't CI ready.

Angular CLI out of the box gives you a few unit tests and an end to end (e2e) test. This is great because you can generate a project and set up your build server to build the artefacts. This is where I ran into problems.

Having everything generated for you is great until something you want to do does not work; and this is where I was. I wanted to build and test my angular application on a headless build agent. The generated code from Angular CLI runs tests using Google Chrome by default. Which is fine, but running Google Chrome on a bui

rjmunro

var a = require('./module1');
var b = require('./module2');

// import a from './module1';
// import b from './module2';

console.log('a',a);
console.log('b',b);

scabbiaza

// How it works: https://youtu.be/IbfsvI6dh4U

@textFontSize: 20px;
@lineHeight: 1.5rem;

// Set up font size and line-height
html {
   font-size: @textFontSize;
}

danwit

/**
 * Simple authentication and authorization example with passport, node_acl,
 *  MongoDB and expressjs
 *
 * The example shown here uses local userdata and sessions to remember a
 *  logged in user. Roles are persistent all the way and applied to user
 *  after logging in.
 *
 * Usage:
 *  1. Start this as server