honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/public/docs
History
Patrice Chalin ad95b04e69 docs(dev guide): pipes - new Dart prose, update Dart and Ts code (#1353) 
+ guide/pipes/ts: update docs and example code

+ guide/pipes/dart: new prose, updated example code

+ fix platform_directives reference; html cleanup

+ enable pipes e2e testing
For `e2e-spec.js`: If the async test is executed too early it will fail
(simply because the async message hasn’t been received yet).

+ follow new constants naming convention
2016-05-13 21:44:14 +01:00
..
_examples
docs(dev guide): pipes - new Dart prose, update Dart and Ts code (#1353)
2016-05-13 21:44:14 +01:00
_includes
docs(sidenav reorg): remove glossary and cheatsheet from REFERENCE. Move glossary to BASICS. Rename REFERENCE to API REFERENCE
2016-04-25 14:10:57 -07:00
dart/latest
docs(dev guide): pipes - new Dart prose, update Dart and Ts code (#1353)
2016-05-13 21:44:14 +01:00
js/latest
docs(cb-webpack): add guide chapter about webpack
2016-05-12 17:22:14 -07:00
ts/latest
docs(dev guide): pipes - new Dart prose, update Dart and Ts code (#1353)
2016-05-13 21:44:14 +01:00
_data.json
docs(api): fix api nav issue #927
2016-03-08 10:46:03 -08:00
_layout.jade
docs: left nav is driven by _data.json files
2016-03-04 19:54:27 -08:00
index.jade
docs(api): fix api nav issue #927
2016-03-08 10:46:03 -08:00
README.md
shred and watch build tooling - v2 ( dgeni, gulp, jade)
2015-08-07 14:49:35 -07:00

README.md

Why the _fragments dir is checked in

Within this repo files generated as a result of shredding the _examples dir ( the contents of the _fragments dir) are checked in so that we can avoid running the shredder over the entire _examples dir each time someone refreshes the repo ( the shred-full gulp task). The gulp serve-and-watch shredder is only a ‘partial’ shredder. It only shred’s files in directories changed during the current session.