Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(244)

Unified Diff: third_party/pkg/angular/lib/routing/module.dart

Issue 148453003: Updating Angular version (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Created 6 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/pkg/angular/lib/routing/module.dart
diff --git a/third_party/pkg/angular/lib/routing/module.dart b/third_party/pkg/angular/lib/routing/module.dart
index 6e14146ea3d8840c39a92c011301e4f501d29c3d..e32c9682ace503ed2081fec7b7d877693f49c44d 100644
--- a/third_party/pkg/angular/lib/routing/module.dart
+++ b/third_party/pkg/angular/lib/routing/module.dart
@@ -1,10 +1,10 @@
/**
- * Routing library makes it easier to build large single-page application. The
+ * The [routing] library makes it easier to build large single-page applications. The
* library lets you map the browser address bar to semantic structure of your
* application and keeps them in sync.
*
- * Angular uses [route_hierarchical] package to define application routes and
- * provides custom tools that it easier to use routing with Angular templates.
+ * Angular uses the [route_hierarchical] package to define application routes and
+ * to provide custom tools to make it easier to use routing with Angular templates.
*
* Lets consider a simple recipe book application. The application might have
* the following pages:
@@ -72,8 +72,8 @@
*
* <view-recipe></view-recipe>
*
- * The template contains a custom `view-recipe` component that handles the
- * displaying of the recipe. Now, our `view-recipe` can inject [RouteProvider]
+ * The template contains a custom `view-recipe` component that handles
+ * displaying the recipe. Now, our `view-recipe` can inject [RouteProvider]
* to get hold of the route and its parameters. It might look like this:
*
* @NgComponent(...)
@@ -184,8 +184,8 @@ class NgRoutingModule extends Module {
/**
* Allows configuration of [Router.useFragment]. By default [usePushState] is
- * true, so router will be listen to [Window.onPopState] and route URLs like
- * "http://host:port/foo/bar?baz=qux". Both path and query parts of the URL
+ * true, so the router will listen to [Window.onPopState] and route URLs like
+ * "http://host:port/foo/bar?baz=qux". Both the path and query parts of the URL
* are used by the router. If [usePushState] is false, router will listen to
* [Window.onHashChange] and route URLs like
* "http://host:port/path#/foo/bar?baz=qux". Everything after hash (#) is used
« no previous file with comments | « third_party/pkg/angular/lib/playback/playback_http.dart ('k') | third_party/pkg/angular/lib/tools/expression_extractor.dart » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698