angular-docs-cn/packages/examples
cexbrayat bef27f2a28 docs(forms): use a number as input value for formControlName (#30606)
PR #29473 changed the docs to use a string as the input value of `formControlName`, as it used to only accept a string.
This has been changed, and `formControlName` now accepts a string or a number, so the example in the docs can use a binding as they used to.

PR Close #30606
2019-08-13 14:21:25 -07:00
..
common build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
compiler build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00
core build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
forms docs(forms): use a number as input value for formControlName (#30606) 2019-08-13 14:21:25 -07:00
http build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00
platform-browser build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00
router/activated-route build: update to rules_nodejs 0.32.2 (#31325) 2019-07-01 14:16:42 -07:00
service-worker/registration-options build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
test-utils build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) 2019-02-28 12:06:36 -08:00
testing build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) 2019-02-28 12:06:36 -08:00
upgrade build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
BUILD.bazel build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00
README.md build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00
index.html build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00
tsconfig-e2e.json build: switch example e2e tests to bazel (#28402) 2019-01-28 19:21:09 -08:00

README.md

API Examples

This folder contains small example apps that get in-lined into our API docs. Each example contains tests for application behavior (as opposed to testing Angular's behavior) just like an Angular application developer would write.

Running the examples

# Serving individual examples (e.g. common)
yarn bazel run //packages/examples/common:devserver

# "core" examples
yarn bazel run //packages/examples/core:devserver

Running the tests

yarn bazel test //packages/examples/...