mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00

Files

T

Paul Gschwendtner 30c002bc88 refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

The way the benchmarking code is used and wired up in g3 is rather
magical. This change makes it easier to sync into g3 by using
conditional blocks, and also consistnetly using a single bundle name
(like it was before— we regressed here as part of the ESM initial
changes- but now with clear comments, it's more future-proof..)

PR Close #48538

2022-12-19 20:12:38 +00:00

change_detection

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

class_bindings

build: update dev-infra packages and account for build-tooling split from ng-dev (#46976 )

2022-08-02 09:37:37 -07:00

expanding_rows

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

js-web-frameworks

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

largeform

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

largetable

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

old

refactor(core): remove unused logic from reflection capabilities (#45335 )

2022-03-24 11:02:39 -07:00

styling

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

tree

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

views

refactor: make benchmarking syncing easier and add comments for future insight (#48538 )

2022-12-19 20:12:38 +00:00

BUILD.bazel

build: remove unused systemjs bootstrap benchmark scripts (#48538 )

2022-12-19 20:12:38 +00:00

README.md

…

util.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:26:58 -04: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.