From 0ef0d836cc8040704b13242e79609979e99ba4f2 Mon Sep 17 00:00:00 2001 From: gnukev Date: Wed, 18 Jan 2017 16:51:02 +0530 Subject: [PATCH] Update component name in the example Updating from "CustomDetail" => "CustomerDetail" under the "Component Instantiation Through Dependency Injection (DI)" section to match the code block --- doc/article/en-US/creating-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/article/en-US/creating-components.md b/doc/article/en-US/creating-components.md index 46d63487..7252b5c2 100644 --- a/doc/article/en-US/creating-components.md +++ b/doc/article/en-US/creating-components.md @@ -84,7 +84,7 @@ Now you know how to build basic components. What's great about this knowledge? I View-models and other interface elements, such as Custom Elements and Custom Attributes, are created as classes which are instantiated by the framework using a dependency injection container. Code written in this style is easy to modularize and test. Rather than creating large classes, you can break things down into small objects that collaborate to achieve a goal. The DI can then put the pieces together for you at runtime. -In order to leverage DI, you simply decorate your class to tell the framework what it should pass to its constructor. Here's an example of a CustomDetail component that depends on Aurelia's fetch client. +In order to leverage DI, you simply decorate your class to tell the framework what it should pass to its constructor. Here's an example of a CustomerDetail component that depends on Aurelia's fetch client.