parent
15c2a93f14
commit
d0e086a5fe
|
@ -83,7 +83,7 @@ HTTP guide.
|
|||
|
||||
## Testing: added component test plunkers (2016-12-02)
|
||||
|
||||
Added two plunkers that each test _one simple component_ so you can write a component test plunker of your own: <live-example name="setup" plnkr="quickstart-specs">one</live-example> for the QuickStart seed's `AppComponent` and <live-example name="testing" plnkr="banner-specs">another</live-example> for the Testing guide's `BannerComponent`.
|
||||
Added two plunkers that each test _one simple component_ so you can write a component test plunker of your own: <live-example name="setup" stackblitz="quickstart-specs">one</live-example> for the QuickStart seed's `AppComponent` and <live-example name="testing" stackblitz="banner-specs">another</live-example> for the Testing guide's `BannerComponent`.
|
||||
Linked to these plunkers in [Testing](guide/testing#live-examples) and [Setup anatomy](guide/setup-systemjs-anatomy) guides.
|
||||
|
||||
## Internationalization: pluralization and _select_ (2016-11-30)
|
||||
|
|
|
@ -54,7 +54,7 @@ If you do, this page can help you understand their purpose.
|
|||
the bootstrap file, `main.ts`.
|
||||
|
||||
Try the <live-example name="setup">sample application</live-example>
|
||||
and the <live-example name="setup" plnkr="quickstart-specs">unit test</live-example>
|
||||
and the <live-example name="setup" stackblitz="quickstart-specs">unit test</live-example>
|
||||
as _live examples_.
|
||||
</td>
|
||||
|
||||
|
|
|
@ -110,13 +110,13 @@ Try this <live-example></live-example>.
|
|||
<p>live-example with name</p>
|
||||
<live-example name="testy" title="Better Example"></live-example>
|
||||
|
||||
<p>live-example with spacey name and plnkr</p>
|
||||
<live-example name=" testy " plnkr="super-plnkr"></live-example>
|
||||
<p>live-example with spacey name and stackblitz</p>
|
||||
<live-example name=" testy " stackblitz="super-stackblitz"></live-example>
|
||||
|
||||
<p>live-example with name and plnkr but no download</p>
|
||||
<live-example name="testy" plnkr="super-plnkr" noDownload></live-example>
|
||||
<p>live-example with name and stackblitz but no download</p>
|
||||
<live-example name="testy" stackblitz="super-stackblitz" noDownload></live-example>
|
||||
|
||||
<p>live-example embedded with name and plnkr</p>
|
||||
<live-example embedded name="testy" plnkr="super-plnkr"></live-example>
|
||||
<p>live-example embedded with name and stackblitz</p>
|
||||
<live-example embedded name="testy" stackblitz="super-stackblitz"></live-example>
|
||||
|
||||
<p>More text follows ...</p>
|
||||
|
|
|
@ -12,13 +12,18 @@ $ yarn upgrade-interactive --tilde
|
|||
|
||||
There, select all the packages that are updated on the new Angular release.
|
||||
|
||||
**2)** Changes to the tsconfig.json? There is one to update at `/aio/tools/examples/shared/boilerplate/src/tsconfig.json`
|
||||
**2)** Changes to the tsconfig.json? There are several files in `/aio/tools/examples/shared/boilerplate/*/tsconfig.json` (based on the example type).
|
||||
|
||||
**3)** The file `/aio/tools/examples/shared/boilerplate/src/systemjs.config.web.js` contains the configuration for plunkers. It has some hardcoded versions that could be updated.
|
||||
**3)** The files `/aio/tools/examples/shared/boilerplate/systemjs/src/systemjs.config.web[.build].js` contains the configuration for plunkers. They have some hardcoded versions that could be updated.
|
||||
|
||||
>N.B.: Plunkers have been replaced by Stackblitz and (almost) all examples have be replaced by CLI/WebPack-based examples that do not use SystemJS.
|
||||
The upgrade examples may still rely on SystemJS.
|
||||
|
||||
**4)** As in step 3, more hardcoded versions at `/aio/tools/plunker-builder/translator/rules/indexHtml.js`
|
||||
|
||||
>Note the same caveat about migration from plunker to Stackblitz.
|
||||
---
|
||||
> NOTE(gkalpak):
|
||||
> There are some `package.json` files in `/aio/tools/examples/shared/boilerplate/*`.
|
||||
> AFAICT, they are copied over to the examples (based on the example type), but they are neither
|
||||
> used for installing dependencies (which come from `/aio/tools/examples/shared/package.json`) nor
|
||||
> used in zips (since they are overwritten by `/aio/tools/example-zipper/customizer`).
|
||||
> For all stackblitz live-examples, `/aio/tools/examples/shared/boilerplate/cli/package.json` seems
|
||||
> to be used.
|
||||
|
|
Loading…
Reference in New Issue