docs: update docs to use HttpClientModule instead of HttpModule (#22727)

Updated most examples to use HttpClientModule instead of deprecated HttpModule

fix #19280

PR Close #22727
This commit is contained in:
Aaron Gussman
2018-03-13 01:53:27 -04:00
committed by Victor Berchet
parent b275d378df
commit b5533e0ee5
8 changed files with 17 additions and 20 deletions

View File

@ -18,8 +18,7 @@ If you use the CLI to generate an app, the default `AppModule` is as follows:
/* JavaScript imports */
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';
import { AppComponent } from './app.component';
@ -29,9 +28,7 @@ import { AppComponent } from './app.component';
AppComponent
],
imports: [
BrowserModule,
FormsModule,
HttpModule
BrowserModule
],
providers: [],
bootstrap: [AppComponent]
@ -137,8 +134,8 @@ It tells Angular about other NgModules that this particular module needs to func
This list of modules are those that export components, directives, or pipes
that the component templates in this module reference. In this case, the component is
`AppComponent`, which references components, directives, or pipes in `BrowserModule`,
`FormsModule`, or `HttpModule`.
`AppComponent`, which references components, directives, or pipes in `BrowserModule`.
Other common components in the examples are `FormsModule` and `HttpClientModule`.
A component template can reference another component, directive,
or pipe when the referenced class is declared in this module or
the class was imported from another module.

View File

@ -36,7 +36,7 @@ The following is an example of specifying a bootstrapped component,
imports: [
BrowserModule,
FormsModule,
HttpModule,
HttpClientModule,
AppRoutingModule
],
providers: [],