ngx-restangular | Restangular for Angular 2 and higher versions | REST library

Solution: If the front-end component is attempting to use Restangular, the Jasmine test must import the Restangular Module. Like this:

My solution for this problem was creating an array of the requests that are pending for the refreshedToken. So when I get a 401 error (access token expired), I request for a new token and also make a flag = true. While this flag is true, I add the requests to the array. When the new token was resolved, I replace the token to the requests in the array, and then repeat them.

Here is my code:

app.module.ts

The setup for prerender and runtime server-side render is mostly similar, the only difference is one is static, the other dynamic. You will still configure everything Universal requires you to set up for it to work.

Before I go into your questions, I highly recommend you to follow this (step-by-step configurations) and this (useful sections about Angular Universal pitfalls) guides to configure Angular Universal as it is one of the more comprehensive and up-to-date write ups that I've read.

First question: How can I create a html file for each of these levels by using prerender.js and How should my static.paths.ts look like?

Your static.path.ts should contain all routes that you want to prerender:

There appears to be a problem with ngx-restangular 2.2.3 and ng ejects > webpack.config.js

Problem solved by using package.json > "ngx-restangular": "2.3.0-beta.3"

First remove or uninstall ngx-restangular, then Just change your package json file like this :

First try to remove Caret(^) from infront of the version number

Why do you need to use a ReplySubject? It seems you are using it just to emit the new access token.

If this is the case, and if I do not miss something, then you could reach the same result in a simpler way, like

It is possible. I got this working by invoking withConfig for each method to be added:

I had a similar problem in my application and I solved it this way:

Subscribers keep waiting for source to emit a value and dont do anything till then

We can use this behavior to solve our problem.

What we can do is something like this :

All HTTP Calls :

You are building that put URL someway wrong, notice last part of it /[object%20Object] that's how javascript print an object reference.

I believe it was supposed to be an id, so it would be /projects/55 for example.

Accordingly to restangular documentation, customPUT([elem, path, params, headers]), second param is a path, that's why you are getting that problem, you are passing an object to a path

change {'id': project.id} to project.id if you would like to have an url like /projects/55