ngResource incorrectly parses string arrays into char arrays

[adam-g-pullen]

I have an "activity" resource along with the standard GET/PUT/DELETE operations, the resource has metadata attached to it one example is "dates" (a list unique dates for all activities)

The current implementation of nsResource incorrectly interprets the return as an array of char arrays, when it should be an array of strings

Below is an example of the implementation using typeof.
It is in the then method of the $http({ call

if (data) {
  if (action.isArray) {
    value.length = 0;
    forEach(data, function(item) {
      if (typeof item == 'string') {
        value.push(item);
      } else {
         value.push(new Resource(item));
      }
    });
  } else {
    copy(data, value);
  }
}

[james-m-henderson]

I just started using angular and I noticed the same issue. This very much seems like a bug to me.

[dungvn3000]

I'm having same problem. I'm using angluarjs ver 1.1.5

[phanhongphucit]

I also have the same problem with version Angular 1.15 . Could you please check it? :(

[kabb5]

Still seeing this problem with 1.2.1 :(

[victorb]

Had the same issue as the people here. Colleague found a thread in the Google Group describing why this is behaving like it does.

Resource is an OO wrapper over your data. For example Book would be a resource. So that you can do

var book = new Book();
book.save()

Since book is an object, having primitive types makes no sense.
https://groups.google.com/d/msg/angular/QjhN9-UeBVM/dYtuMcvD55EJ

Which makes sense. Either you have resources where your backend would return a object (or a array of objects) or you use $http to get a array of strings (or whatever you want).

[linclark]

VictorBjelkholm posted the explanation, so this seems like works as expected to me.