@for and ngFor reporting errors but still iterating over data about angular HOT 5 CLOSED

Hi, I'm not sure what the issue is. You're not handling an error, what would you expect ?

from angular.

We will definitely need a reproduction in Stackblitz in order to investigate further. I suspect whatever data library you're using is returning an object that isn't actually an Array (maybe a proxy?) [Symbol.iterator] should definitely be a function for any collection that @for supports.

from angular.

I'll see whether I can put one together. As noted it only seems to happen when using the response from the API.
Checking all the points through the code (browser debug console, console logging & dumping the JSON) shows it as an array.
The API endpoint is written in nest.js, so is also typescript based. I've hard-coded the data in the API to be an array to make sure that's what was being returned, but it still fails.

from angular.

@alxhub Based on your comment about a proxy I changed the code to use the API directly and it works. Seems to be something in how I've implemented ngrx/store which is causing the error.

Once I've found the problem I'll add a comment here in case anyone else comes across the same thing.

Thanks for the help.

from angular.

The issue was down to a typo in the definition of the initial state object.

Instead of "array: <Type[]>[];" it was "array: <Type[]>{};" so the initial value in the store was not an array type., causing the error.

from angular.