I am trying to use material dropdown select but I am getting this error:
EXCEPTION: No provider found for DomPopupSourceFactory.
The materialDirectives is added to the directives list, the html call is simple:
<material-dropdown-select></material-dropdown-select>
I tried the angular_components_example and it worked fine. The problem is with my project. I already tried to clean the .packages and executed the pub get. Nothing worked. I tried some other material components and they worked.
If you add materialProviders to AppComponent it should work:
#Component(
selector: 'my-app',
directives: const <dynamic>[
CORE_DIRECTIVES,
materialDirectives,
],
providers: const <dynamic>[
materialProviders, // <<<<<<<<<<<<<<<<
],
)
class AppComponent {...}
It works in angular_components example because the app-level component includes the necessary popupBindings provider.
If you aren't including materialProviders in your app, you can use a more specific provider in your components.
Here is the minimum boilerplate required for using material-dropdown-select:
import 'package:angular/angular.dart';
import 'package:angular_components/laminate/popup/module.dart';
import 'package:angular_components/material_select/material_dropdown_select.dart';
#Component(
selector: 'my-dropdown-select',
directives: const [
MaterialDropdownSelectComponent,
],
providers: const [
popupBindings,
],
)
class MyDropdownSelectComponent {}
Related
I already checked the link NestJs dependency injection with task scheduling is not working but that is not the same problem that I have since I'm not using request scope on the on my injectable service.
I recorded a loom video to show the issue.
https://www.loom.com/share/37875a6e0d79400698a4408ef8d9ac89
Thanks
Tiago
Solved. Thanks to #Micael Levi.
The problem was the provider array on AppModule. It was instantiating the ReckonService again.
Example of the ReckonModule after fix:
#Module({
imports: [HttpModule],
controllers: [ReckonController],
providers: [ReckonService],
exports: [ReckonService],
})
export class ReckonModule {}
Example of the AppModule after fix:
#Module({
imports: [ReckonModule],
controllers: [],
providers: [AppService],
})
export class AppModule {}
Thanks
Tiago
I'm working on an Angular 5 project (which I generated with the Angular CLI), using Bower for front-end dependencies. All the dependencies I need for my project are custom polymer components. I originally was able to get this project to work by using the Origami project, however I'm finding that I'd rather not use the project if possible since Polymer 2 and Angular 5 are meant to work quite well together now. The only place I've used the Origami project is in app.module.ts, where I import the PolymerModule from #codebakery/origami like so:
app.module.ts:
import { NgModule, CUSTOM_ELEMENTS_SCHEMA } from '#angular/core';
import { HttpModule } from '#angular/http';
import { BrowserModule } from '#angular/platform-browser';
import { FormsModule } from '#angular/forms';
import { PolymerModule } from '#codebakery/origami';
import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { AnalysisComponent } from './analysis/analysis.component';
import { DashboardComponent } from './dashboard/dashboard.component';
import { SemtkService } from './services/semtk.service';
#NgModule({
declarations: [
AppComponent,
AnalysisComponent,
DashboardComponent
],
schemas: [ CUSTOM_ELEMENTS_SCHEMA ],
imports: [
HttpModule,
BrowserModule,
AppRoutingModule,
FormsModule,
PolymerModule.forRoot() // Only import .forRoot() once and at the highest level
],
providers: [ SemtkService ],
bootstrap: [ AppComponent ]
})
export class AppModule { }
In trying to delete the origami project, I've commented out the line PolymerModule.forRoot(), from the imports array. When I do this, the Polymer components seem to loose their styling.
Here is the page WITH the PolymerModule.forRoot() import:
page WITH import
And here is the page WITHOUT the import:
page WITHOUT import
Any ideas about what I could do to fix this would be welcome - thanks!
Author of Origami here, there's a service the library provides at the application root that registers Angular component styles with ShadyCSS (needed for #apply mixin support for all browsers and custom properties for browsers that don't support them).
https://github.com/hotforfeature/origami/blob/v2/origami/src/style/shared-styles-host.ts
You could either include that one service and provide it at your app's root, or write your own service that does something similar. Once Angular's styles are registered with ShadyCSS, any variables/mixins you define in Angular will be applied in Polymer.
i have a sample mvc5 project and i used my first angular 2 modules successfully on this project. now i want to create new module inside my mvc areas. so i created new area with a .tsfile named app.components in my area solution! like what you see below:
import { Component } from '#angular/core';
#Component({
selector: 'area-app',
template:`<p>imanArea</p>`
})
export class areacomponent {<<bring below error!!!!!!!!!!!
name = 'dd';
}
experimental support for decorators is a feature
that is subject to change in a future release. set the
'experimentaldecorators' option to remove this warning
and second is from my root project rootproj/app/app.module.ts
import { NgModule } from '#angular/core';
import { BrowserModule } from '#angular/platform-browser';
import { FormsModule } from '#angular/forms'; // <-- NgModel lives here
import { AppComponent } from './app.component';
***below error for this line***
import { AreaAppComponent } from './Areas/SampleArea/app/app.areacomponent'
#NgModule({
imports: [BrowserModule, FormsModule],
declarations: [ AppComponent ],
bootstrap: [ AppComponent ]
})
export class AppModule { }
Cannot find module'./Areas/SampleArea/app/app.areacomponent'
i checked my path and file names!! every thing is right but it doesn't find my path!
for more information i have to say all my essential angular files are in my root project and my app.module is inside a folder named app
means: rootProj/app/app.module and rootProj/app/app.component.spec
is it possible to use angular2 and mvc-Area together in one project?? i didnt find any source about that.
I actually use WebAPI to use Angular 2.
Back and Front-End are going to be in different project folders. And you will work with restful services.
I have problem with injecting singleton service into a directive.
I have service:
#Injectable()
export class AuthService{ ... }
I put it into bootstrapper.
bootstrap(AppComponent, [AuthService, ...]);
I made directive, that protects my component:
#Directive({
selector: '[protected]'
})
export class ProtectedDirective {
constructor(private authService:AuthService) { ... }
}
... and added to one of components
#Component({
selector: 'dashboard',
directives: [ProtectedDirective],
template: '<div protected></div',
})
export class DashboardCmp { }
In console i see an error:
ORIGINAL EXCEPTION: No provider for AuthService!
If I add a provider to DashboardCmp, everything works fine, but it's not a singleton service. I set its properties in other component and I don't see them when I'm in directive.
I resolved my problem. Everything was fine but
import {AuthService} from '../services/auth.service'; (in protected.directive.ts)
is not equal to
import {AuthService} from '../Services/auth.service'; ( in main.ts)
Yes, it's stupid, but it made the dependency injection impossible.
I have a NavBar Component which loads the QApi Service, the QApi Service loads the UserService, but I get the following error:
EXCEPTION: No provider for UserService! (NavBarComponent -> QApi -> UserService)
Either I simply don't get the concept of dependency injection, I made a stupid error, or this is just way to complicated compared to native development... Thanks for your help.
Here my code:
UserService:
import {Injectable} from 'angular2/core';
//import {User} from '../data-source-mocks/users';
#Injectable()
export class UserService {
public isAuthenticated = true;
}
QApi Service:
import {Injectable} from 'angular2/core';
import {UserService} from '../user/user.service';
#Injectable()
export class QApi {
constructor(private _userService: UserService) {}
}
NavBar Component:
import {Component} from 'angular2/core';
import {QApi} from '../../services/q-api/q-api';
#Component({
selector: 'nav-bar',
template: `Test NavBar`,
providers: [QApi]
})
export class NavBarComponent {
private _isAuthenticated = false;
constructor(private _QApi: QApi) {}
}
EDIT:
First of all: Thanks for alle the great answers each and every single one helped me to understand dependency injection better, especially this article: https://angular.io/docs/ts/latest/guide/hierarchical-dependency-injection.html
I changed my QApi class to this:
import {Injectable, Inject, Injector} from 'angular2/core';
import {UserService} from '../user/user.service';
import {CardService} from '../card/card.service';
#Injectable()
export class QApi {
constructor() {
var _injector = Injector.resolveAndCreate([UserService,
CardService]);
this.userService = _injector.get(UserService);
this.cardService = _injector.get(CardService);
}
}
Now it works like I hoped it would. Cant thank you guys enough!!
Add UserService to the component providers:
#Component({
selector: 'nav-bar',
template: `Test NavBar`,
providers: [QApi, UserService] // <- add UserService here
})
export class NavBarComponent { /* ... */ }
Here are two good articles to better understand Angular2 Dependency Injection:
blog.thoughtram.io: Dependency Injection in Angular2
blog.thoughtram.io: Injecting services in services in Angular 2
In fact both previous responses are true! ;-)
You need to define the services:
Application level. Within the second parameter of the bootstrap function. It contains the list of the providers that are available for the whole application.
bootstrap(App, [UserService, QApi, ...]);
Component level. Within the providers attribute of the Component annotation. In this case, this is only configured for this component and you need to define this for each component where the QApi service.
#Component({
selector: 'nav-bar',
template: `Test NavBar`,
providers: [QApi, UserService]
})
You also mix things. I mean you can put the UserService provider at the application level and QApi at the component level. In fact what is important is that Angular can find providers for all the involved elements in the processing chaining (with dependency injection). They can come from either component level (1st) or application level (2nd).
Hope that it gives you some additional hints following alexpods and MichaelOryl great answers ;-)
Thierry
List the services in your bootstrap call (wherever you are handling that). Something like the following should work:
bootstrap(App, [UserService, QApi, COMMON_DIRECTIVES, ROUTER_DIRECTIVES, ROUTER_PROVIDERS, HTTP_PROVIDERS]);
providers// directives added here are available to all children
Then you will have a single instance of each of those services available to the rest of your application.