21fe9dc1d2
# Conflicts: # README.md # public/docs/js/latest/cookbook/ts-to-js.jade # public/docs/ts/latest/cookbook/a1-a2-quick-reference.jade # public/docs/ts/latest/guide/architecture.jade # public/docs/ts/latest/guide/attribute-directives.jade # public/docs/ts/latest/guide/forms.jade # public/docs/ts/latest/guide/lifecycle-hooks.jade # public/docs/ts/latest/guide/router.jade # public/docs/ts/latest/guide/server-communication.jade # public/docs/ts/latest/guide/style-guide.jade # public/docs/ts/latest/guide/template-syntax.jade # public/docs/ts/latest/testing/first-app-tests.jade # public/docs/ts/latest/tutorial/toh-pt5.jade # public/docs/ts/latest/tutorial/toh-pt6.jade # public/news.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.