By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
module.exports = { | |
extends: ['./commitlint.mobile.js'], | |
parserPreset: './parser-preset' | |
}; |
import { NgModule } from '@angular/core'; | |
import { | |
MdButtonModule, | |
MdCardModule, | |
MdListModule, | |
MdMenuModule, | |
MdPaginatorModule, | |
MdProgressBarModule, | |
MdSidenavModule, | |
MdSnackBarModule, |
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
<!DOCTYPE html> | |
<meta charset="utf-8"> | |
<title>SANKEY Experiment</title> | |
<style> | |
.node rect { | |
cursor: move; | |
fill-opacity: .9; | |
shape-rendering: crispEdges; | |
} |
border: no | |
license: Apache-2.0 |
license: mit |
license: mit |
import { Pipe, PipeTransform } from '@angular/core'; | |
/** | |
* usage: *ngFor="let item of data | key" | |
*/ | |
@Pipe({ | |
name: 'keys' | |
}) | |
export class KeysPipe implements PipeTransform { | |
/** | |
* @param value - object of objects |
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.