d034bc33c8
# Conflicts: # public/contribute.jade # public/docs/js/latest/cookbook/ts-to-js.jade # public/docs/ts/latest/cookbook/_data.json # public/docs/ts/latest/cookbook/component-communication.jade # public/docs/ts/latest/cookbook/component-relative-paths.jade # public/docs/ts/latest/cookbook/dependency-injection.jade # public/docs/ts/latest/cookbook/dynamic-form.jade # public/docs/ts/latest/cookbook/set-document-title.jade # public/docs/ts/latest/glossary.jade # public/docs/ts/latest/guide/forms.jade # public/docs/ts/latest/guide/pipes.jade # public/docs/ts/latest/guide/router.jade # public/docs/ts/latest/guide/user-input.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.