AngularJS 1.2.0 $http not preserving array elements

Question

I've recently upgraded to AngularJS 1.2.0, and there a problem with passing array that breaks the site. In an example $http request I am passing fields like so:

$http.get({
                url : 'users',
                data : {
                    fields : 'user_id, user_name',
                    conditions : {
                        customer_id : current_site_id
                    },
                    join : ['customer_users']
                }
            });

In the last stable release of 1.0.8, the [] for the join was preserved, so in the php side it showed up as array and was iterable. In 1.2.0, the array is removed and the parameters pass as such by the browser to the server:

conditions:{"customer_id":"9a83a3db-673e-407f-9a0d-1f804c4dcd01"}
fields:user_id, user_name
join:customer_users //<---- THIS SHOULD BE AN ARRAY!

Because its not an iterable object, it breaks the php side. So aside from renaming all array variables from ['xyz'] to {'0': 'xyz'}, to mimic the array behavior though not optimal, how can I ensure angularJS passes the value as an array?

Oliver · Accepted Answer · 2013-11-15 16:39:16Z

1

I think your example should not work at all. It should be this:

$http({
    method: 'GET',
    url : 'users',
    params : {
        fields : 'user_id, user_name',
        conditions : {
            customer_id : current_site_id
        },
        join : ['customer_users']
    }
});

And angular does the right job parsing the url since 1.1.1. The spec says if you have an array it'll be parsed like this ?join=item1&join=item2. If the array only have one item it'll be ?join=item1.

On the other hand jQuery.param() will parse it like this: ?join[]=item1&join[]=item2 And it - if I'm right - will ensure that $_GET['join'] always be an array.

All in all, try 'join[]' : ['customer_users']. It might work.

answered Nov 15, 2013 at 16:39

Oliver

4,4712 gold badges23 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Devin Dixon Over a year ago

A possible solution but that solution also requires me to go through each $http I making and modifying it. Doable yes but not optimal.

Oliver Over a year ago

Well, you can always intercept the request. (docs.angularjs.org/api/ng.$http#description_interceptors) In a request interceptor, you'll have a config.params. Feel free to transform as you wish.

Devin Dixon Over a year ago

Thanks! Thats a much better solution I can write

Collectives™ on Stack Overflow

AngularJS 1.2.0 $http not preserving array elements

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related