iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/modules/benchmarks/src
History
Wagner Maciel 90a2796a7e revert: "build(core): use dev-infra's component_benchmark to show PoC (#36434)" (#36798) 
This reverts commit e6161ca307be01eb1142092b53cbd7ddbd33312a.

PR Close #36798
2020-04-24 11:03:37 -07:00
..
change_detection
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
class_bindings
revert: "build(core): use dev-infra's component_benchmark to show PoC (#36434)" (#36798)
2020-04-24 11:03:37 -07:00
expanding_rows
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
js-web-frameworks
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
largeform
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
largetable
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
old
build: reformat repo to new clang@1.4.0 (#36613)
2020-04-14 12:08:36 -07:00
styling
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
tree
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)
2020-04-23 13:31:53 -07:00
views
build: reformat repo to new clang@1.4.0 (#36613)
2020-04-14 12:08:36 -07:00
bootstrap_ng2.ts
build: reformat repo to new clang@1.4.0 (#36613)
2020-04-14 12:08:36 -07:00
bootstrap_plain.ts
build: reformat repo to new clang@1.4.0 (#36613)
2020-04-14 12:08:36 -07:00
BUILD.bazel
style: enforce buildifier lint on CI (#28186)
2019-02-26 16:57:41 -08:00
README.md
build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788)
2018-07-24 08:26:16 -07:00
util.ts
build: reformat repo to new clang@1.4.0 (#36613)
2020-04-14 12:08:36 -07:00

README.md

Benchmark Directory Layout

Bazel

Under bazel the rules for laying out test files are slightly different. Use largetable/render3 as an example.

Put the perf file in current subdirectory (ie largetable) such that the same perf file can be used for each of the sub-subdirectories. (ie largetable/* should all be testable with the same perf file largetable/largetable_perf.spec.ts). Under bazel, typescript protractor spec files must end with .spec.ts or .test.ts.