Angular 2 stable - @NgModule design

The big change in RC5 was the move to modules. It moves away from declaring directives and services in components to declaring them in “module files”. This actually lines up well with the angular.module function of ng1. Here my initial idea of how this could be mapped. Any thoughts?

@NgModule({
  declarations: [ AwesomePipe, HighlightDirective, TitleComponent ], // components, directives, filters
  providers: [ UserService ], // provided services
  imports: [ SharedModule, 'ngAnimate' ], // module dependencies
  exports: [ HighlightDirective, UserService, SharedModule ] // shows what is intended to be public
})

• declarations - registers components directives and pipe classes with angular.module(...).directive() or .filter()
• providers - registers services via angular.module(...).service()
• imports - modules to register in angular.module(..., [dependencies]) (could be decorated module or string)
• exports - show what declarations are intended to be used in other modules (even though ng1 makes all declarations public)
• bootstrap - root component to place in dom
• entryComponents - not needed?

References:

https://angularjs.blogspot.com/2016/08/angular-2-rc5-ngmodules-lazy-loading.html https://angular.io/docs/ts/latest/guide/ngmodule.html https://angular.io/docs/ts/latest/cookbook/rc4-to-rc5.html https://docs.angularjs.org/api/ng/function/angular.module https://docs.angularjs.org/api/ng/type/angular.Module

[Hotell]

@aciccarello @JamesHenry I would include whole API, and explicitly state in source code docs and Markdown docs, that they don’t do anything as for now ( maybe later we can provide some mechanism to emit warnings or errors when someone uses something from some feature module and didn’t exported that component/directive/pipe etc… )

It will enforce the right Angular 2 architecture mindset. Leaving comments is not very good idea IMHO.

[aciccarello]

maybe later we can provide some mechanism to emit warnings or errors when someone uses something from some feature module and didn’t exported that component/directive/pipe etc…

👍 That’s a great idea. Maybe it could be a flag similar to ng1 strict dependency injection.