ae3b205c77
# Conflicts: # public/docs/ts/latest/cookbook/_data.json # public/docs/ts/latest/guide/_data.json # public/docs/ts/latest/guide/attribute-directives.jade # public/docs/ts/latest/guide/component-styles.jade # public/docs/ts/latest/guide/hierarchical-dependency-injection.jade # public/docs/ts/latest/guide/style-guide.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
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.