Web worker translation #40129
Closed
Web worker translation #40129
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed the way to express the idea from "usted" to "tu"
* docs: translate the app-shell.md file * Update aio/content/guide/app-shell.md Co-authored-by: Christian Morante <christianmorante@outlook.com> * Update aio/content/guide/app-shell.md Co-authored-by: Christian Morante <christianmorante@outlook.com> * Update aio/content/guide/app-shell.md Co-authored-by: Christian Morante <christianmorante@outlook.com> * add PR feedback * docs: update 'usted'-'tú' (Grammatical person) Co-authored-by: Christian Morante <christianmorante@outlook.com>
Traducción del README.md al español.
Co-authored-by: Pato <11162114+devpato@users.noreply.github.com>
Co-authored-by: Pato <11162114+devpato@users.noreply.github.com>
Co-authored-by: Alejandro Lora <alejandrofpo@gmail.com> Co-authored-by: Andrés Villanueva <andresvillanuevab@gmail.com> Co-authored-by: Michael Prentice <splaktar@gmail.com>
* Traducido Traducido el apartado "Accesibilidad en Angular". Pendiente de revisión. * Update aio/content/guide/accessibility.md Co-authored-by: Pato <11162114+devpato@users.noreply.github.com> * Update aio/content/guide/accessibility.md Co-authored-by: Pato <11162114+devpato@users.noreply.github.com> * Update aio/content/guide/accessibility.md Co-authored-by: Pato <11162114+devpato@users.noreply.github.com> * Update aio/content/guide/accessibility.md Co-authored-by: Pato <11162114+devpato@users.noreply.github.com> Co-authored-by: Pato <11162114+devpato@users.noreply.github.com>
This commit fixes the spelling of the singular form of the word function to the plural spelling in packages/core/src/application_init.ts PR Close angular#36586
Developer docs previously stated to use `yarn bazel test //packages/...` which attempts to test all packages with View Engine (the default), even though not all support View Engine. This updates the doc to use `yarn test-ivy-aot` and `yarn test-non-ivy` which tests both Ivy and View Engine while filtering out tests which are not compatible with each renderer. PR Close angular#38149
…io and docs examples (angular#38173) There were two `typings.d.ts` files with SystemJS module definitions in `aio/src/` and `aio/tools/examples/shared/boilerplate/cli/`. These are remnants from old CLI versions that used SystemJS and are no longer needed. For docs examples specifically, these files were never copied over to example projects and thus not included in StackBlitz projects and ZIP archives. This commit removes these obsolete files. PR Close angular#38173
…iles from docs examples (angular#38173) There were some `systemjs.config.web[.build].js` files in the `systemjs` boilerplate directory that are not used any more. In the past, these files were used in the Plunker-based live examples, but we no longer use Plunker for live examples. This commit removes these obsolete files. PR Close angular#38173
… `i18n` docs examples (angular#38173) Docs examples of type `i18n` need a slightly modified version of `polyfills.ts` that imports `@angular/localize/init`. Previously, this file was not included in `i18n` example projects for two reasons: - While the file was included in the `i18n` boilerplate files (at `aio/tools/examples/shared/boilerplate/i18n/`), it was not included in the boilerplate file list in `example-boilerplate.js`. - The file was in the wrong location: It was located at the project root instead of inside the `src/` directory. This commit addresses the above issues (i.e. adds the file to the boilerplate file list for `i18n` projects and moves the file inside the `src/` directory). PR Close angular#38173
…angular#38173) Previously, the `.gitignore` file that is part of the boilerplate files for CLI-based docs examples (located in `aio/tools/examples/shared/boilerplate/cli/`) was not added to the example projects, because it was not included in the boilerplate file list in `example-boilerplate.js`. This commit fixes it by adding the `.gitignore` file to the list. This ensures that docs examples more closely match CLI-generated projects. PR Close angular#38173
…rplate.js` (angular#38173) To avoid unnecessary code duplication in docs examples, we have some boilerplate files for various example types (in `aio/tools/examples/shared/boilerplate/`). These files are copied to each example project in `aio/content/examples/` (according to the example's type, as specified in its `example-config.json` file). Previously, the `example-boilerplate.js`, which is responsible for copying the boilerplate files, had lists for files to be copied for each project type and only copied the listed files from the boilerplate directory to the example directory. This approach had some drawbacks: - Files need to be updated in two separate locations: in the boilerplate directory that includes the files and the file list in `example-boilerplate.js`. - It is easy to add a file in the boilerplate directory but forget to add it in `example-boilerplate.js` and not realize that it is not being included in the example project (including the generated StackBlitz project and ZIP archive). This commit changes the approach by removing the boilerplate file listings from `example-boilerplate.js` and copying all files from a boilerplate directory to example directories. This addresses the above drawbacks and simplifies the `example-boilerplate.js` script. I have verified that the resulting code example doc regions as well as the generated StackBlitz projects and ZIP archives are identical to the ones generated before this commit. PR Close angular#38173
- Se agrego la versión en ingles .en.md Fixes #78
pullapprove
bot
requested review from
alxhub,
crisbeto,
IgorMinar,
jessicajaniuk,
mhevery and
petebacondarwin
pullapprove
bot
added
area: animations
area: core
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information