-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom interceptor is not called #1875
Comments
Hi @crissty. Do you have errors in dev tools console? Probably related to akveo/nebular#631. |
Same problem here, need to include on each lazy module providers with interceptor to get it working. |
So what do you mean by latest release? is it master? or what? master is never latest unless you pull. So far my interceptors are working. As a matter of fact i am going to start a new project now based on the latest master branche. So i will let you know if i run in any problems with regards to your question. Show us your code so we can have a look at it. Quote: "Same problem here, need to include on each lazy module providers with interceptor to get it working." <- as i said show us your code. The reason i ask for code is because if you dont do DI properly your service will be instantiated as new and not for Root. I hope you understand where i am going with this. |
I've had this problem as well. |
I have the same problem with the following code in
I am importing The Using Angular 7 |
This worked for me:
|
@stenterwan In the github repository of ng2-completer someone opened an issue for the same problem. They deleted the HttpClientModule import in versión I change my package.json and it's works, me and my partner created an issue !! |
An awesome find. I struggled for 2 days to make my Interceptor work. Finally, your tip did the trick. As stated by @IgnacioYanjari, I've updated ng2-completer to 3.0.0-beta.2. Interceptor works without any issues now. |
Hi @nileshnagarwal I just wondering, updating ng2-completer to latest stable version, now is 3.0.2 will solve this problem? so I've mean, Is there no need then to import and add the interceptor into each module as a provider? |
Hi @BruneXX I've been using ng2-completer version 3.0.0-beta.2 and have only added the interceptor to the providers in app.module.ts. No need to import it in each module separately. |
Hi @nileshnagarwal excellent, I can confirm that it works with ng2-completer v3.0.2 thanks for your quick reply! :) |
Issue type
I'm submitting a ... (check one with "x")
Issue description
Current behavior:
I have a custom interceptor of angular included in AppModule, when I update the ngx-admin, the interceptor is not working, it is not called in several routes or it is call more than once.
Expected behavior:
The interceptor should be called in every call.
Steps to reproduce:
Update ngx-admin to last release.
Related code:
Other information:
npm, node, OS, Browser
Angular, Nebular
The text was updated successfully, but these errors were encountered: