honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/public/docs
History
Naomi Black 61db4a09a9 docs(alpha-36): update api for alpha-36 renames 2015-09-01 13:55:47 -07:00
..
_examples Karma configuration and sample test 2015-08-13 15:39:18 -07:00
_fragments First pass at build-shred-map complete 2015-08-13 15:39:16 -07:00
_includes harp(update): var changes to allow use with harp 0.17.0 2015-07-28 00:14:34 -07:00
dart/latest angular.dart -> angular2.dart in quickstart text 2015-08-03 07:37:10 -07:00
js/latest docs(alpha-36): update api for alpha-36 renames 2015-09-01 13:55:47 -07:00
README.md shred and watch build tooling - v2 ( dgeni, gulp, jade) 2015-08-07 14:49:35 -07:00
_data.json added alerts style 2015-03-04 05:21:10 -08:00
_layout.jade use one layout, update logic, add prettify to api code tags 2015-05-03 20:28:21 -07:00
index.jade ordered guide 2015-04-16 07:24:28 -07:00
styleguide.jade hide side nag for now 2015-04-13 05:46:14 -07:00
xref-frag-to-jade.html clean up regionExtractor to hoist nullLine pattern, 2015-08-13 15:39:16 -07:00
xref-jade-to-frag.html clean up regionExtractor to hoist nullLine pattern, 2015-08-13 15:39:16 -07:00
xref-jade.json clean up regionExtractor to hoist nullLine pattern, 2015-08-13 15:39:16 -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.