0303a18020
# Conflicts: # README.md # public/docs/ts/latest/guide/attribute-directives.jade # public/docs/ts/latest/guide/component-styles.jade # public/docs/ts/latest/guide/dependency-injection.jade # public/docs/ts/latest/guide/hierarchical-dependency-injection.jade # public/docs/ts/latest/guide/lifecycle-hooks.jade # public/docs/ts/latest/guide/pipes.jade # public/docs/ts/latest/guide/security.jade # public/docs/ts/latest/guide/server-communication.jade # public/docs/ts/latest/guide/structural-directives.jade # public/docs/ts/latest/quickstart.jade # public/docs/ts/latest/testing/testing-an-angular-pipe.jade # public/docs/ts/latest/tutorial/index.jade # public/docs/ts/latest/tutorial/toh-pt1.jade # public/docs/ts/latest/tutorial/toh-pt2.jade # public/docs/ts/latest/tutorial/toh-pt3.jade # public/docs/ts/latest/tutorial/toh-pt4.jade # public/docs/ts/latest/tutorial/toh-pt5.jade # public/docs/ts/latest/tutorial/toh-pt6.jade
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.