Rob Wormald recognized that we had no plunker for a simple component test. Inspired improved learning path for testing including:
* Add plunkers for both inline and external template versions of the simplest `BannerComponent`
* Added the banner-specs for that purpose and also a quickstart-specs in the setup folder
* Adjusted prose in testing and setup-systemjs-anatomy to call these out
* Moved testing of external template spec earlier in the guide because it is likely to be needed right away.
* Add comments on the optional "testing" folder and corrects var names to match
* Leaves Jasmine Spec Runner output visible when tests finish
* update docs home banner
* update example and main repo pubspec.yaml files
* update shredder tests
(Not strictly necessary, but avoids tripping regex triggers when doing
updates.)
For specific plunkers, e.g. "QuickStart (reboot edition)" PR #2762, that shouldn't have AppModule or main.ts
Rescinds the automatic bootstrapping and exclusion of `main.ts` in #2786 and #2756
Only autoBootstraps when `window.autoBootstrap === true`.
Contributes to #2407
- Dropped the “2” in “Angular 2” and “angular2_*” where appropriate.
- Did a partial sync of `_cache/guide/pipes.jade`
- In quickstart, changed `Try changing the message to "Hello Angular
2!”` to `Try changing the message to "Hello Again Angular!”`.
* plunker builder removes files and scripts not needed in plunkers (e.g., systemjs.config.js)
* no longer adds placeholder README.md (deemed a distraction)
* tag is now "Angular" instead of "Angular2"
* new plnkr.json "includeSystemConfig" option adds systemjs.config.js back; needed for testing plnkrs.
* incidentally changes comment "Polyfill(s)" to "Polyfills" in all index.html
Bug in Jasmine v.2.5.x. Stick with v.2.4.1 (as karma-jasmine does) until the following issue is resolved:
https://github.com/jasmine/jasmine/issues/1231
Unfortunately, there is no `@types/jasmine` for v.2.4 but only for v.2.5.
- gulp task: don’t copy over internal libraries.
- Adjust anchor hrefs rather than use `<base href>` in generated API
pages. The net effect is the same.
* chore(test): add protractor4
* fix lint, remove boilerplate files, fix less gen
* separate scripts between package.json
* ignore a2docs.css in boilerplate
* remove tslint in _examples
- Use custom bootstrap grid system styles
- Cache a copy of the dartdoc static-assets styles.css w/ footer styles
disabled.
- Alternate page layout controlled by jade2ng harp global
The update to dgeni-packages led to a breaking change in the Nunjucks
templates, where macros are now isolated from their calling site.
This means that we must pass the `versionInfo` object through to the
macro rather than expecting it to be in scope already.
Iterate through the docs and merge all the of metadata docs
for each decorator doc into the decorator doc and remove it
so that it is not rendered in a page of its own