From 00efac58cbe310d2fbe1fad9c7e509109aecd666 Mon Sep 17 00:00:00 2001 From: Fanks Date: Sat, 3 Oct 2020 20:44:57 -0500 Subject: [PATCH 1/2] docs: translate frequent-ngmodules.md --- aio/content/guide/frequent-ngmodules.md | 80 ++++++++++++------------- 1 file changed, 40 insertions(+), 40 deletions(-) diff --git a/aio/content/guide/frequent-ngmodules.md b/aio/content/guide/frequent-ngmodules.md index 75701a67f6e9..c9bc0a1b3949 100644 --- a/aio/content/guide/frequent-ngmodules.md +++ b/aio/content/guide/frequent-ngmodules.md @@ -1,10 +1,9 @@ -# Frequently-used modules - -An Angular app needs at least one module that serves as the root module. -As you add features to your app, you can add them in modules. -The following are frequently used Angular modules with examples -of some of the things they contain: +# Módulos utilizados frecuentemente +Una app de Angular requiere al menos un módulo que funciona como el módulo raíz. +Puedes agregar nuevas funcionalidades a tu app enforma de módulos. +A continuación encontrarás módulos frecuentemente utilizados en Angular +con ejemplos de lo que contienen: @@ -14,63 +13,63 @@ of some of the things they contain: - + - + - + - + - + - +
- Import it from + Impórtalo desde - Why you use it + Para que sirve
BrowserModule @angular/platform-browserWhen you want to run your app in a browserPermite correr tu app en un navegador
CommonModule @angular/commonWhen you want to use NgIf, NgForPermite utilizar NgIf, NgFor
FormsModule @angular/formsWhen you want to build template driven forms (includes NgModel)Permite utlizar formularios basados en plantillas (incluye NgModel)
ReactiveFormsModule @angular/formsWhen you want to build reactive formsPermite crear formularios reactivos
RouterModule @angular/routerWhen you want to use RouterLink, .forRoot(), and .forChild()Permite utlizar RouterLink, .forRoot(), y .forChild()
HttpClientModule @angular/common/httpWhen you want to talk to a serverPermite comunicarte con un servidor
-## Importing modules +## Importación de módulos -When you use these Angular modules, import them in `AppModule`, -or your feature module as appropriate, and list them in the `@NgModule` -`imports` array. For example, in the basic app generated by the [Angular CLI](cli), -`BrowserModule` is the first import at the top of the `AppModule`, -`app.module.ts`. +Al utilizar estos módulos de Angular, importalos dentro de `AppModule`, +o en tu modulo de funcionalidades en caso de ser necesario, y enlístalos +en el array de `imports` de `@NgModule`. Por ejemploe, en la app básica +generada por la [Angular CLI](cli), `BrowserModule` es el primero en ser importado +al inicio de `AppModule`, `app.module.ts`. ```typescript -/* import modules so that AppModule can access them */ +/* importa los módulos de manera que AppModule pueda accederlos */ import { BrowserModule } from '@angular/platform-browser'; import { NgModule } from '@angular/core'; @@ -80,7 +79,7 @@ import { AppComponent } from './app.component'; declarations: [ AppComponent ], - imports: [ /* add modules here so Angular knows to use them */ + imports: [ /* agrega los módulos aquí para que Angular pueda utilizarlos */ BrowserModule, ], providers: [], @@ -89,27 +88,28 @@ import { AppComponent } from './app.component'; export class AppModule { } ``` -The imports at the top of the array are JavaScript import statements -while the `imports` array within `@NgModule` is Angular specific. -For more information on the difference, see [JavaScript Modules vs. NgModules](guide/ngmodule-vs-jsmodule). +Los imports al inicio del array son declaraciones de importación de Javascript +mientras que el array de `imports` dentro de `@NgModule` es específico de Angular. +Para más información sobre sus diferencias, consulta [JavaScript Modules vs. NgModules](guide/ngmodule-vs-jsmodule). -## `BrowserModule` and `CommonModule` +## `BrowserModule` y `CommonModule` -`BrowserModule` imports `CommonModule`, which contributes many common -directives such as `ngIf` and `ngFor`. Additionally, `BrowserModule` -re-exports `CommonModule` making all of its directives available -to any module that imports `BrowserModule`. +`BrowserModule` importa a `CommonModule`, el cual contibuyte con muchas +directivas comunes como `ngIf` y `ngFor`. Adicionalmente, `BrowserModule` +exporta nuevamente a `CommonModule` haciendo que todas sus directivas +estén disponibles a cualquier módulo que importe a `BrowserModule`. -For apps that run in the browser, import `BrowserModule` in the -root `AppModule` because it provides services that are essential -to launch and run a browser app. `BrowserModule`’s providers -are for the whole app so it should only be in the root module, -not in feature modules. Feature modules only need the common -directives in `CommonModule`; they don’t need to re-install app-wide providers. +Para apps que corran en el navegador, importa `BrowserModule` en la +raíz `AppModule` ya que así proveerá los servicios escenciales para +iniciar y correr la app en el navegador. Los proveedores de `BrowserModule` +son para toda la aplicación por lo que debería de estar sólamente dentro +del módulo raíz, no en módulos de funcionalidades. Los módulos de funcionalidades +solamente necesitan de las directivas comunes encontradas en `CommonModule`; +no necesitan volver a instalar proveedores que sirven para toda la aplicación. -If you do import `BrowserModule` into a lazy loaded feature module, -Angular returns an error telling you to use `CommonModule` instead. +Si llegas a importar `BrowserModule` dentro de un módulo de funcionalidad +con carga diferida, Angular regresará un error diciéndote que utilizes `CommonModule`.
BrowserModule error @@ -118,9 +118,9 @@ Angular returns an error telling you to use `CommonModule` instead.
-## More on NgModules +## Más sobre NgModules -You may also be interested in the following: +Puede que estés interesado en lo siguiente: * [Bootstrapping](guide/bootstrapping). * [NgModules](guide/ngmodules). * [JavaScript Modules vs. NgModules](guide/ngmodule-vs-jsmodule). From 08e9c4512df6ceaba54a9c72519cbe0de7516e62 Mon Sep 17 00:00:00 2001 From: Fanks Date: Sat, 3 Oct 2020 21:02:30 -0500 Subject: [PATCH 2/2] docs: se ajusta la traduccion de (#153) --- aio/content/guide/frequent-ngmodules.en.md | 126 ++++++++++++++++++ ...-ngmodules.md => frequent-ngmodules.es.md} | 0 2 files changed, 126 insertions(+) create mode 100644 aio/content/guide/frequent-ngmodules.en.md rename aio/content/guide/{frequent-ngmodules.md => frequent-ngmodules.es.md} (100%) diff --git a/aio/content/guide/frequent-ngmodules.en.md b/aio/content/guide/frequent-ngmodules.en.md new file mode 100644 index 000000000000..75701a67f6e9 --- /dev/null +++ b/aio/content/guide/frequent-ngmodules.en.md @@ -0,0 +1,126 @@ +# Frequently-used modules + +An Angular app needs at least one module that serves as the root module. +As you add features to your app, you can add them in modules. +The following are frequently used Angular modules with examples +of some of the things they contain: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ NgModule + + Import it from + + Why you use it +
BrowserModule@angular/platform-browserWhen you want to run your app in a browser
CommonModule@angular/commonWhen you want to use NgIf, NgFor
FormsModule@angular/formsWhen you want to build template driven forms (includes NgModel)
ReactiveFormsModule@angular/formsWhen you want to build reactive forms
RouterModule@angular/routerWhen you want to use RouterLink, .forRoot(), and .forChild()
HttpClientModule@angular/common/httpWhen you want to talk to a server
+ +## Importing modules + +When you use these Angular modules, import them in `AppModule`, +or your feature module as appropriate, and list them in the `@NgModule` +`imports` array. For example, in the basic app generated by the [Angular CLI](cli), +`BrowserModule` is the first import at the top of the `AppModule`, +`app.module.ts`. + + +```typescript +/* import modules so that AppModule can access them */ +import { BrowserModule } from '@angular/platform-browser'; +import { NgModule } from '@angular/core'; + +import { AppComponent } from './app.component'; + +@NgModule({ + declarations: [ + AppComponent + ], + imports: [ /* add modules here so Angular knows to use them */ + BrowserModule, + ], + providers: [], + bootstrap: [AppComponent] +}) +export class AppModule { } +``` + +The imports at the top of the array are JavaScript import statements +while the `imports` array within `@NgModule` is Angular specific. +For more information on the difference, see [JavaScript Modules vs. NgModules](guide/ngmodule-vs-jsmodule). + + +## `BrowserModule` and `CommonModule` + +`BrowserModule` imports `CommonModule`, which contributes many common +directives such as `ngIf` and `ngFor`. Additionally, `BrowserModule` +re-exports `CommonModule` making all of its directives available +to any module that imports `BrowserModule`. + +For apps that run in the browser, import `BrowserModule` in the +root `AppModule` because it provides services that are essential +to launch and run a browser app. `BrowserModule`’s providers +are for the whole app so it should only be in the root module, +not in feature modules. Feature modules only need the common +directives in `CommonModule`; they don’t need to re-install app-wide providers. + +If you do import `BrowserModule` into a lazy loaded feature module, +Angular returns an error telling you to use `CommonModule` instead. + +
+ BrowserModule error +
+ +
+ + +## More on NgModules + +You may also be interested in the following: +* [Bootstrapping](guide/bootstrapping). +* [NgModules](guide/ngmodules). +* [JavaScript Modules vs. NgModules](guide/ngmodule-vs-jsmodule). diff --git a/aio/content/guide/frequent-ngmodules.md b/aio/content/guide/frequent-ngmodules.es.md similarity index 100% rename from aio/content/guide/frequent-ngmodules.md rename to aio/content/guide/frequent-ngmodules.es.md