-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actualizar Angular de 10.0.2 a 10.1.3 #291
base: master
Are you sure you want to change the base?
Conversation
This commit updates the version of Angular CLI used in angular.io to version 10.1.3. PR Close angular#39017
This commit updates the version of Angular framework used in angular.io to version 10.1.3. NOTE: The actual size decrease for the main bundle is 3KB (because the actual size before this commit was 451226B, not 450952B as seen in `aio-payloads.json`). PR Close angular#39017
This commit updates the version of Angular Components used in angular.io to version 10.2.2. NOTE: The actual size increase for the main bundle in ViewEngine mode is 1.3KB (because the actual size before this commit was 430423B, not 430008B as seen in `aio-payloads.json`). PR Close angular#39017
…est CLI (angular#39017) This commit updates TypeScript and other dependencies used in angular.io to more closely align with new apps created with the latest Angular CLI. It also updates `tsconfig.json`, re-ordering some properties around and introducing some more checks (again to more closely match new CLI apps). NOTE: I skipped updating RxJS from 6.5.4 to 6.6.3, because it increased the main bundle by ~500B. NOTE: `tslint.json` will be updated in a subsequent PR, because it requires more extensive changes. PR Close angular#39017
Notes Paul and Pawel as OOO through commenting out their usernames in users entries throughout the pullapprove configs which could result in their review being requested by pullapprove. PR Close angular#39028
This commit updates the copy and headers to bring in line with style guide and clarify content. PR Close angular#38742
…rker-dynamic (angular#38846) Remove @angular/platform-webworker and @angular/platform-webworker-dynamic as they were deprecated in v8 BREAKING CHANGE: @angular/platform-webworker and @angular/platform-webworker-dynamic have been removed as they were deprecated in v8 PR Close angular#38846
…vent (angular#38985) Instead of doing all sorts of checks in the `visit()` method, move checks that are specific to `BoundEvent` to the `visitBoundEvent()` method. PR Close angular#38985
…les in `aio/tools/` (angular#38992) This commit updates the Markdown files inside the `aio/tools/` directory to contain one sentence per line in order to be consistent with how Markdown files are formatted in the rest of the repo. PR Close angular#38992
…es boilerplate (angular#38992) When updating the boilerplate for CLI-based docs examples, one needed to install dependencies inside the `aio/tools/examples/shared/boilerplate/cli/` directory, which resulted in a `node_modules/` directory and a `yarn.lock` file. These were not supposed to be part of the boilerplate, so they had to be manually removed after the boilerplate was updated. This commit simplifies the workflow by allowing boilerplate files to be ignored (both by git and the `example-boilerplate.js` script) via a `.gitignore` file. This way, it is no longer necessary to manually remove the unneeded directories/files. PR Close angular#38992
…ilerplate (angular#38992) Previously, when updating the dependency versions in `aio/tools/examples/shared/package.json` (which contains all dependencies used in docs examples projects), one had to manually go through all boilerplate directories and update the `package.json` files with the same versions. This commit simplifies this task by automating it via a Node.js script. PR Close angular#38992
…le (angular#39002) This commit adds an API to `NgCompiler`, a method called `getComponentsWithTemplateFile`. Given a filesystem path to an external template file, it retrieves a `Set` (actually a `ReadonlySet`) of component declarations which are using this template. In most cases, this will only be a single component. This information is easily determined by the compiler during analysis, but is hard for a lot of Angular tooling (e.g. the language service) to infer independently. Therefore, it makes sense to expose this as a compiler API. PR Close angular#39002
…ore fields (angular#39033) In preparation for the Ivy Language service, add the same properties to AppComponent that appear in TemplateReference so the inline template can be tested thoroughly. PR Close angular#39033
…nce (angular#39034) In order to keep document consistency this commit replaces a comma with a period at the end of a sentence PR Close angular#39034
…lder (angular#39035) This commit updates ngbot config to avoid requesting google3 presubmit for the changes in the `packages/compiler-cli/src/ngtsc/sourcemaps` folder (which is not synced into google3). PR Close angular#39035
…n Ivy (angular#39036) Currently it is impossible to determine the source of a binding that generates `BoundAttribute` because all bound attributes generated from a microsyntax expression share the same source span. For example, in ```html <div *ngFor="let item of items; trackBy: trackByFn"></div> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ source span for all `BoundAttribute`s generated from microsyntax ``` the `BoundAttribute` for both `ngForOf` and `ngForTrackBy` share the same source span. A lot of hacks were necessary in View Engine language service to work around this limitation. It was done by inspecting the whole source span then figuring out the relative position of the cursor. With this change, we introduce a flag to set the binding span as the source span of the `ParsedProperty` in Ivy AST. This flag is needed so that we don't have to change VE ASTs. Note that in the binding parser, we already set `bindingSpan` as the source span for a `ParsedVariable`, and `keySpan` as the source span for a literal attribute. This change makes the Ivy AST more consistent by propagating the binding span to `ParsedProperty` as well. PR Close angular#39036
Change the word "weather" to "whether" PR Close angular#39041
…ular#39045) Updating [angular#master](https://github.com/angular/angular/tree/master) from [cli-builds#master](https://github.com/angular/cli-builds/tree/master). ## Relevant changes in [commit range](angular/cli-builds@bc6369c...568d34c): **Modified** - help/xi18n.json PR Close angular#39045
…ne=compile (angular#39046) Removes the failure message put in place to catch usages of the old --define=compile method of setting which compiler was to be used. PR Close angular#39046
* Add `templateNode` to `ElementSymbol` and `TemplateSymbol` so callers can use the information about the attributes on the `TmplAstElement`/`TmplAstTemplate` for directive matching * Remove helper function `getSymbolOfVariableDeclaration` and favor more specific handling for scenarios. The generic function did not easily handle different scenarios for all types of variable declarations in the TCB PR Close angular#39047
…ngular#39050) Create stubs for getTypeDefinitionAtPosition for both VE and Ivy Language Service implementations. This will prevent failed requests when it is implemented on the vscode plugin side PR Close angular#39050
…ngular#39051) For rebase tooling, use the `GitClient`'s `checkout` method rather than a custom function doing the same task. PR Close angular#39051
…ular#39059) Updating [angular#master](https://github.com/angular/angular/tree/master) from [cli-builds#master](https://github.com/angular/cli-builds/tree/master). ## Relevant changes in [commit range](angular/cli-builds@568d34c...e526da6): **Modified** - help/test.json PR Close angular#39059
…rosyntax (angular#39062) It used to be the case that all microsyntax bindings share the same source span, so the second bound attribute would overwrite the first. This has been fixed in angular#39036, this case is added to prevent regression. PR Close angular#39062
Update the derived locales based on the new CLDR data. PR Close angular#39343
The type of the `navigationExtras` param was accidetally changed to the wrong symbol in angular@783a5bd. These changes revert it to the correct one. PR Close angular#39347
Upgrade the karma dependency to version 4.4.0 in the root package.json and in integration tests. Compared to version 4.3.0, which most of the packages were previously depending on, it has the following changes: Bug Fixes - runner: remove explicit error on all tests failed Features - client: Add trusted types support - Preprocessor can return Promise - config: add failOnSkippedTests option. - config: clientDisplayNone sets client elements display none. - deps: Remove core-js dependency. The motivation for upgrading the package is the Trusted Types support that it adds, which is necessary to enable Trusted Types in Angular's unit tests. PR Close angular#39180
This commit edits the property binding doc copy and adds some docregions to clarify explanations. PR Close angular#38799
) This change also remove the duplicate mention of strictTemplates PR Close angular#39353
Commit type Style is still present in Commiit Message Header while it shouldn't PR Close angular#39357
…ular#39359) Updating [angular#master](https://github.com/angular/angular/tree/master) from [cli-builds#master](https://github.com/angular/cli-builds/tree/master). ## Relevant changes in [commit range](angular/cli-builds@e53ced0...9d53eac): **Modified** - help/build.json - help/generate.json - help/serve.json - help/update.json - help/xi18n.json PR Close angular#39359
This commit fixes a bug when `useAbsoluteUrl` is set to true and `ServerPlatformLocation` infers the base url from the supplied `url`. User should explicitly set the `baseUrl` when they turn on `useAbsoluteUrl`. Breaking change: If you use `useAbsoluteUrl` to setup `platform-server`, you now need to also specify `baseUrl`. We are intentionally making this a breaking change in a minor release, because if `useAbsoluteUrl` is set to `true` then the behavior of the application could be unpredictable, resulting in issues that are hard to discover but could be affecting production environments. PR Close angular#39334
Updates to the latest version of bazel PR Close angular#39351
…#39233) `TemplateFixture` used to have positional parameters and many tests got hard to read as number of parameters reach 10+ with many of them `null`. This refactoring changes `TemplateFixture` to take named parameters which improves usability and readability in tests. PR Close angular#39233
) `i18n_spec.ts` file was incorrectly in the `render3` folder rather than `render3/i18n` PR Close angular#39233
…#39233) Before this refactoring/fix the ICU would store the current selected index in `TView`. This is incorrect, since if ICU is in `ngFor` it will cause issues in some circumstances. This refactoring properly moves the state to `LView`. closes angular#37021 closes angular#38144 closes angular#38073 PR Close angular#39233
angular#39233) This is a pre-requisite for making the `TNode.value` a generic storage mechanism for attaching data to `TNode`. PR Close angular#39233
…ngular#39233) Remove casting where we stored `TIcu` in `TNode.tagName` which was of type `string` rather than `TIcu'. (renamed to `TNode.value` in previous commit.) PR Close angular#39233
…TView` debug (angular#39233) When looking at `TView` debug template only Element nodes were displayed as `TNode.Element` was used for both `RElement` and `RText`. Additionally no text was stored in `TNode.value`. The result was that the whole template could not be reconstructed. This refactoring creates `TNodeType.Text` and store the text value in `TNode.value`. The refactoring also changes `TNodeType` into flag-like structure make it more efficient to check many different types at once. PR Close angular#39233
…ngular#39233) Previous function name `debugMatch` was not consistent with other match functions. PR Close angular#39233
`COMMENT_MARKER` is a generic name which does not make it obvious that it is used for ICU use case. `ICU_MARKER` is more explicit as it is used exclusively with ICUs. PR Close angular#39233
- Made `*OpCodes` array branded for safer type checking. - Simplify `I18NRemoveOpCodes` encoding. - Broke out `IcuCreateOpCodes` from `I18nMutableOpCodes`. PR Close angular#39233
…ons only) (angular#39233) IMPORTANT: `HEADER_OFFSET` should only be refereed to the in the `ɵɵ*` instructions to translate instruction index into `LView` index. All other indexes should be in the `LView` index space and there should be no need to refer to `HEADER_OFFSET` anywhere else. PR Close angular#39233
…gular#39233) `expandoInstructions` uses negative numbers by `-x`. This has lead to issues in the paste as `-0` is processed as float rather than integer leading to de-optimization. PR Close angular#39233
Moved code from `interfaces/i18n.ts` which was causing circular dependencies PR Close angular#39233
…0.1.3 # Conflicts: # .circleci/config.yml # .github/ISSUE_TEMPLATE/1-bug-report.md # .github/ISSUE_TEMPLATE/2-feature-request.md # .github/ISSUE_TEMPLATE/5-support-request.md # .github/ISSUE_TEMPLATE/6-angular-cli.md # .github/ISSUE_TEMPLATE/7-angular-components.md # .ng-dev/commit-message.ts # CODE_OF_CONDUCT.md # CONTRIBUTING.md # README.md # aio/README.md # aio/content/guide/architecture-modules.md # aio/content/guide/architecture-next-steps.md # aio/content/guide/architecture-services.md # aio/content/guide/architecture.md # aio/content/guide/attribute-binding.md # aio/content/guide/bootstrapping.md # aio/content/guide/glossary.md # aio/content/guide/ngmodules.md # aio/content/guide/template-statements.md # aio/content/marketing/analytics.md # aio/content/marketing/docs.md # aio/content/marketing/events.html # aio/content/navigation.json # aio/content/tutorial/toh-pt4.md # aio/content/tutorial/toh-pt6.md # aio/package.json # aio/src/app/shared/ga.service.spec.ts # aio/src/app/shared/ga.service.ts # aio/src/app/shared/location.service.spec.ts # aio/tests/e2e/src/onerror.e2e-spec.ts # aio/yarn.lock
|
Lista de Verificación del PR
Comprueba si tu PR cumple los siguientes requisitos:
Tipo de PR
¿Qué tipo de cambio introduce este PR?
¿Cuál es el comportamiento actual?
¿Cuál es el nuevo comportamiento?
TODO
Estos archivos deben revisarse para detectar cambios. Muchos, quizás todos, deben agregarse a los archivos
.en.md
. Algunos de los conflictos también deben resolverse en los archivos traducidos.