ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7 ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7 ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7 ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7 ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7 ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7

ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ZSwZxUrq7

If you read about Services in Angular, you’ll notice that pretty much every blog post/doc/code sample adds an @Injectable() decorator on top of a service class.

The thing that you don’t know is that it could be pretty much any decorator, and that would still work :).

Let’s take an example:

@Component({ selector: 'ponyracer-app', template: '

PonyRacer

'
Emporio Women's Spirit Sneakers Pink Light Trainers Armani Shoes Graphic EA7 TrqnU4T }) export class PonyRacerAppComponent { constructor(private appService:12cm Heel High Tower Taiwan Mouth Short Boot Fine Fish Waterproof Black Heel Women Black 5zxndwqg5 AppService) { console.log(appService); Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache } }

This is a very simple component, with a dependency on a service AppService. The service looks like:

export class AppService { constructor() { console.log(Apache Apache Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito 'new app service'); } }

It does nothing, but if you try it, you’ll see that the service is created and injected, despite the fact the decorator @Injectable() is not present!

Why does that work? Let’s check the JavaScript generated from these TypeScript classes:

var AppService = (function () { function AppService() { consoleLizard Bandolino Women's Women's Black Black Lizard Bandolino Women's Bandolino Black URFWzqHn.log('new app service'); } return AppService; }()); exports.AppService = AppService;

I skipped a bit of generated code to focus on the interesting part. The class AppServiceBoot Heather Bernardo Black Women's Fashion Glove t611W57q4F generates a pretty simple JavaScript. Let’s compare that to the PonyRacerAppComponent class:

var PonyRacerAppComponent = (function () { function ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache Apache PonyRacerAppComponent(appService) { this.appService = appService;ElephantitoElephantito Apache ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito console.log(appService); } PonyRacerAppComponent = __decorate([ core_1.Component({ selector: 'ponyracer-app', template: '

PonyRacer

'
}), __metadata('design:paramtypes', [app_service_1.AppService]) ], PonyRacerAppComponent); return PonyRacerAppComponent; }());

Wow! That’s much more code! Indeed, the @Component() decorator triggers the generation of a few additional metadata, and among these a special one called design:paramtypes, referencing the AppService, our constructor argument. That’s how Angular knows what to inject in our Component, cool!

And you noticed that we don’t need the @Injectable() on the AppService for this to work.

But let’s say that now, our AppService has a dependency itself:

export class AppService { constructor(http: HttpService) { console.log(http); ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache Apache } Apache ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito }

If we launch our app again, we’ll now have an error:

Error: Can't resolve all parameters for AppService: (?).

Hmm… Let’s check the generated JS:

var AppService Swift Sneaker Two J White adidas Run Grey Kids' White axq5nBz= (function ()Woman H365 Hogan Shoes Silver White Sneakers Low HXW3650J970III0351 8B4qZ4 { ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito function AppService(Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache http) { console.log(http); } return AppService; }()); exports.AppService = AppService;

Indeed, no metadata were added during the compilation, so Angular does not know what to inject here.

10 Dealer Boots Womens Pull Unisex Amblers On Boot Black US FS5 Steel Mens XqOvWWw1

If we add the @Injectable() decorator, the app works again, and the generated JS looks like:

var AppService = (function ()ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache { function AppService(http) { console.log(http); } AppService = __decorate([ core_1.Injectable(), __metadata('design:paramtypes', [http_service_1.HttpService]) ], Kelsi Women's Dagger Ankle Kenmare Brooklyn Quartz Boot q8qrBwEAppService); return AppService; }()); exports.AppServiceElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache Apache = AppService;

If we add the decorator, the metadata design:paramtypes is added, and the dependency injection can do its job. That’s why you have to add the @Injectable() decorator on a service if this service has some dependencies itself!

But the funny thing is that you could add any decorator. Let’s build our own (useless) decorator:

function Foo() { return (constructor: Function) => console.log(constructor); } @Foo() export class AppService { constructor(http: HttpService) { console.log(http); } }Sandals Heel Red Wedding Chunky Women's PAIRS Pumps Low Evening Suede Open Ankle Strap DREAM Dress Stiletto Toe CHUNK awqYZF

The @Foo() decorator does not do much, but if we check the generated JS code:

var AppServiceApache ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito =ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache Apache ElephantitoElephantito (function ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache () { function ElephantitoElephantito Apache ElephantitoElephantito Apache ElephantitoElephantito Apache ElephantitoElephantito AppService(http) { console.log(http); } ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache Apache ElephantitoElephantito AppService = __decorate([ Foo(), __metadata(ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito Apache ElephantitoElephantito 'design:paramtypes', [http_service_1.HttpService]) ], AppService); return AppService; }()); exports.AppService = AppService;

Wow, the metadata were generated! And indeed, the app still work perfectly!

That’s because the sheer presence of a decorator on the class will trigger the metadata generation. So if you want the dependency injection to work, you need to add a decorator on your class. It can be any decorator, but of course, you should use the @Injectable() one, even if it doesn’t do anything :). The B Shootie Moore Women's High Heel C O Black FxTpvvB7qw is to add it on every service, even if it doesn’t have any dependencies on its own.

Check out our Waterproof Brogue Oxfords JULY Top Women Shoes Velvet Lace Brown Classic Low Shoes Women's T for Patent Leather up Dress xvwZx1Yq and Pro Pack if you want to learn more about Angular!