04ab5edf65
Since #41625, `/guide/updating-to-version-10` is being redirected to `https://v11.angular.io/guide/updating-to-version-11`. However, `v11.angular.io` itself is being redirected to `angular.io`, while v11 is the latest stable version. As a result, `/guide/updating-to-version-10` ends up being redirected to `https://angular.io/guide/updating-to-version-11`. Currently, this causes a CI failure in the `aio_monidoting` job ([example failure][1]). This will change once v12 is released as the new stable version. Alternatively, we could update the config and tests to expected `/guide/updating-to-version-10` to be redirected to `https://angular.io/guide/updating-to-version-11`, but that would end up being redirected to `https://angular.io/guide/updating-to-version-12` once v12 would be released, which is different behavior. This commit provides a way to test for redirects when the destination URL is itself redirected to a different URL. This allows us to use the intended URL (for example, `https://v11.angular.io/...`), which will continue to work as expected regardless of what is the latest stable version without causing CI failures. [1]: https://circleci.com/gh/angular/angular/983738 PR Close #42018 |
||
---|---|---|
.circleci | ||
.devcontainer | ||
.github | ||
.husky | ||
.ng-dev | ||
.vscode | ||
.yarn | ||
aio | ||
dev-infra | ||
docs | ||
goldens | ||
integration | ||
modules | ||
packages | ||
scripts | ||
third_party | ||
tools | ||
.bazelignore | ||
.bazelrc | ||
.bazelversion | ||
.clang-format | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitmessage | ||
.mailmap | ||
.npmrc | ||
.nvmrc | ||
.prettierrc | ||
.pullapprove.yml | ||
.yarnrc | ||
BUILD.bazel | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md | ||
WORKSPACE | ||
browser-providers.conf.js | ||
gulpfile.js | ||
karma-js.conf.js | ||
package.json | ||
renovate.json | ||
test-events.js | ||
test-main.js | ||
tslint.json | ||
yarn.lock | ||
yarn.lock.readme.md |
README.md
Angular - The modern web developer's platform.
Angular is a development platform for building mobile and desktop web applications
using Typescript/JavaScript and other languages.
Contributing Guidelines
·
Submit an Issue
·
Blog
Documentation
Get started with Angular, learn the fundamentals and explore advanced topics on our documentation website.
Advanced
Development Setup
Prerequisites
- Install Node.js which includes Node Package Manager
Setting Up a Project
Install the Angular CLI globally:
npm install -g @angular/cli
Create workspace:
ng new [PROJECT NAME]
Run the application:
cd [PROJECT NAME]
ng serve
Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions.
Quickstart
Ecosystem
Changelog
Learn about the latest improvements.
Upgrading
Check out our upgrade guide to find out the best way to upgrade your project.
Contributing
Contributing Guidelines
Read through our contributing guidelines to learn about our submission process, coding rules and more.
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 labeled as help wanted or good first issue.
Code of Conduct
Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.
Community
Join the conversation and help the community.
Love Angular? Give our repo a star ⭐ ⬆️.