iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3fecab64b1
angular-docs-cn/modules/benchmarks
History
Matias Niemelä d8665e639b refactor(ivy): drop element prefixes for all styling-related instructions () 
This is the final patch to migrate the Angular styling code to have a
smaller instruction set in preparation for the runtime refactor. All
styling-related instructions now work both in template and hostBindings
functions and do not use `element` as a prefix for their names:

BEFORE:
  elementStyling()
  elementStyleProp()
  elementClassProp()
  elementStyleMap()
  elementClassMap()
  elementStylingApply()

AFTER:
  styling()
  styleProp()
  classProp()
  styleMap()
  classMap()
  stylingApply()

PR Close
2019-05-08 15:33:39 -07:00
..
e2e_test/old
build: convert largeform benchmarks to bazel ()
2019-02-13 12:15:01 -08:00
src
refactor(ivy): drop element prefixes for all styling-related instructions ()
2019-05-08 15:33:39 -07:00
benchmark_test.bzl
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles ()
2019-02-28 12:06:36 -08:00
BUILD.bazel
build: update instructions to run benchmark tests ()
2019-02-13 12:15:01 -08:00
README.md
build: update instructions to run benchmark tests ()
2019-02-13 12:15:01 -08:00
start-server.js
build: run tree benchmark tests with bazel ()
2019-02-08 13:37:36 -08:00
tsconfig-build.json
build: serve benchmark tree examples with bazel ()
2019-02-08 13:37:36 -08:00
tsconfig-e2e.json
build: convert largeform benchmarks to bazel ()
2019-02-13 12:15:01 -08:00

README.md

How to run the benchmarks locally

Run in the browser

yarn bazel run modules/benchmarks/src/tree/{name}:devserver

# e.g. "ng2" tree benchmark:
yarn bazel run modules/benchmarks/src/tree/ng2:devserver

Run e2e tests

# Run e2e tests of individual applications:
yarn bazel test modules/benchmarks/src/tree/ng2/...

# Run all e2e tests:
yarn bazel test modules/benchmarks/...

Use of *_aot.ts files

The *_aot.ts files are used as entry-points within Google to run the benchmark tests. These are still built as part of the corresponding ng_module rule.