76104f395f
Previously, cli-based docs examples were tested using `yarn e2e ...`. In some cases, it might make sense to run different or additional checks for a docs example (when running `yarn example-e2e` in `aio/`). Currently, the only option is to define a custom project type and overwrite the `e2e` yarn script in `package.json`. Doing so (in addition to being cumbersome and verbose) would also end up in the `.zip` archive that users can download to run the example locally. This would be confusing, if these custom tests are specific to our CI needs. This commit adds support for defining a custom list of commands per example. These commands (if specified) would be run instead of the default `yarn e2e ...`, when testing the docs examples on CI (via `yarn example-e2e`). (This feature will be used to verify that the `service-worker-getting-started` example is set up correctly in a subsequent commit, but can be useful in other cases as well.) PR Close #28020 |
||
|---|---|---|
| .buildkite | ||
| .circleci | ||
| .github | ||
| aio | ||
| docs | ||
| integration | ||
| modules | ||
| packages | ||
| scripts | ||
| third_party/github.com/bazelbuild/bazel-toolchains/bazelrc | ||
| tools | ||
| .bazelignore | ||
| .bazelrc | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .nvmrc | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| WORKSPACE | ||
| browser-providers.conf.js | ||
| gulpfile.js | ||
| index.bzl | ||
| karma-js.conf.js | ||
| package.json | ||
| protractor-e2e.conf.js | ||
| protractor-examples-e2e.conf.js | ||
| protractor-perf.conf.js | ||
| shims_for_IE.js | ||
| test-events.js | ||
| test-main.js | ||
| tslint.json | ||
| yarn.lock | ||
| yarn.lock.readme.md | ||
README.md
Angular
Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.