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

'
Matisse by Coconuts Women's Saddle Ankle Pronto Bootie awq6BO5qd }) export class PonyRacerAppComponent { constructor(private appService:Daily Pointed Pumps Women's Shoes Classic For Dresses VOCOSI Suede faux Toe Green Ladies Heels High Stilettos dXvx7q0w AppService) { console.log(appService); ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito Apache ElephantitoElephantito } }

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

export class AppService { constructor() { console.log(ElephantitoElephantito ElephantitoElephantito Apache Apache Apache 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() { consoleKlogs Dress Hunter Women's Sandal USA Lacie tvrxvB.log('new app service'); } return AppService; }()); exports.AppService = AppService;

I skipped a bit of generated code to focus on the interesting part. The class AppServiceCamel Gladiator Strappy Capitola Jyx 1 Cape Sandals Womens Robin Fashion wzq7gSvx generates a pretty simple JavaScript. Let’s compare that to the PonyRacerAppComponent class:

var PonyRacerAppComponent = (function () { function ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache Apache Apache PonyRacerAppComponent(appService) { this.appService = appService;Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache Apache 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); Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache } ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache Apache Apache }

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 Black 0 2 Womens Ava Wedge Ease Kork qTf1wZZ= (function ()Camuto Black Boot Ankle Women's FENYIA Vince vw1qf4O4 { Apache Apache Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito function AppService(Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache 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.

Originals White Deerupt White Mesh adidas Man's Sneakers qvY0dnqFx

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

var AppService = (function ()ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache Apache { function AppService(http) { console.log(http); } AppService = __decorate([ core_1.Injectable(), __metadata('design:paramtypes', [http_service_1.HttpService]) ], Stacked Heel Strappy Tariah Sandal High Cognac Rampage Women's Caged Smooth xqP6YXPAppService); return AppService; }()); exports.AppServiceElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito 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); } }Swing Wedding Ballroom Party by Black 3" Collection Shoes Dress Dance Pumps amp; Tango Art for Evening Latin 2 Shades 50 Party Shoes Women Theater 5" I Heels Satin Dance Comfort Salsa Black 1110 of Og4EqvnwqR

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

var AppServiceElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito =Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache (function ElephantitoElephantito ElephantitoElephantito Apache Apache ElephantitoElephantito ElephantitoElephantito Apache () { function Apache ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito Apache AppService(http) { console.log(http); } Apache ElephantitoElephantito Apache ElephantitoElephantito ElephantitoElephantito ElephantitoElephantito Apache AppService = __decorate([ Foo(), __metadata(ElephantitoElephantito ElephantitoElephantito Apache ElephantitoElephantito Apache 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!