No provider for Http! about angular2-jwt HOT 7 CLOSED

Can you try passing Http to the deps array?

...

import {Http} from 'angular2/http';

...

provide(AuthHttp, {
  useFactory: (http) => {
    return new AuthHttp(new AuthConfig(), http);
  },
  deps: [Http]
})

...

Let me know if that works :)

from angular2-jwt.

That does it!!! Thank you! Never would have thought of doing that.

It's been a month or so since I've started with Angular2-jws. Is there any mention of this approach in the docs?

from angular2-jwt.

This is from a recent change. I'll update the readme to reflect it. Thanks!

from angular2-jwt.

You should just be able to provide auth config and authhttp like this:

provide(AuthConfig, {useValue: new AuthConfig()}),AuthHttp

I believe when I pulled the injector out of the AuthHttp constructor I updated the example (though I used a factory and not a value).

from angular2-jwt.

provide(AuthConfig, {useValue: new AuthConfig()}),AuthHttp

This is still not working on my side, beta.8 - i still get an exception:

Cannot resolve all parameters for 'AuthConfig'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'AuthConfig' is decorated with Injectable.

Error: Cannot read property 'getOptional' of undefined

Even if i try to give him the local config param in my provide, the error won't go away. Are now actually Decorators missing in the current AuthConfig implementation?

Update:

I've just copied over the variant to bootstrap from the project page (angular2-jwt):

provide(AuthHttp, { useFactory: (http) => { return new AuthHttp(new AuthConfig({ headerName: 'YOUR_HEADER_NAME', headerPrefix: 'YOUR_HEADER_PREFIX', tokenName: 'YOUR_TOKEN_NAME', tokenGetter: 'YOUR_TOKEN_GETTER_FUNCTION', noJwtError: true }), http); }, deps: [Http] })

Now this variant is working, yay! :) I know, my strings i'm defining for all the values in my config object are total non-sense, i just wanted to make it running first.. but leaving them empty has taken me into another error again (can't remember which one right now)

from angular2-jwt.

It doesn't need to be decorated if you use it via useValue, because you are instantiating it directly.

Can you provide us with your entire bootstrap? Are you providing AuthConfig anywhere else?

You can look at this plunk as well for ideas: http://plnkr.co/edit/pKazgpkXLX9ZgV02YuVf?p=preview

from angular2-jwt.

Thx @escardin for your answer - we crossed each other, i've just made an update on my comment how i could fix it ;)

from angular2-jwt.