fun with arrays in JSON

[firekesti]

Hey community. I haven't been able to figure out how to access part of a piece of data loaded from a store. Here's the JSON:

entity-list:
{
    "id":"1e3f2071638241e292b705c034be4d6b",
        "title": "Planets",
    "entities":
    {
        "data":
        [
            {
                "data":
                {
                    "name":"Earth",
                    "id":"23f03fe70a16aed0d7e210357164e401",
                    }
                }
            },
            {
                "data":
                {
                    "name":"Moon",
                    "id":"23f03fe70a16aed0d7e210357164e339",
                }
            }


        ]
    }
}

For the id, title (and other properties omitted here), it's simple, and I get that.

    config: {
        fields: [
        { name: 'id', type: 'string' },
        { name: 'title', type: 'string' },
        ...etc
        ]
    }

But I'm not sure how to get the "name" part of each of the entities in the list. I've tried several things:

        { name: 'entities', mapping: 'entities.data.data' }, //or entities.data

        hasMany: [
        { name: 'entities', model: 'KT.model.Entity', associationKey: 'entities' }, //or entities.data
        ]

For what it's worth, the Entity model looks like this:

Ext.define('KT.model.Entity', {
    extend: 'Ext.data.Model',


    config: {
        fields: [ 
        { name: 'id', type: 'string' },
        { name: 'name', type: 'string' },
        ]
    }
});

What am I missing?

[firekesti]

{ name: 'entities',         mapping: 'entities.data[0].data["name"]' },

This code works well to give me exactly what I need from one of the elements, but not both - I feel like I should be using hasMany, but not sure how. This is the furthest I've gotten

[siebmanb]

I so understand, I never managed to use the associations for models

After several hours of struggling, I decided to explore the data using a DOM debugger (like the one in Safari or Chrome) and use the complete "address" of the data, which can gives something like this :

Ext.getStore('myStore').getAt(0).data.foo[2].bar[1].value

Dirty but working . If you can get hasMany to work it is much better of course.

[firekesti]

Thanks, I suppose I'll try that out perhaps using 'each' to get all the values, since there is a varying amount across instances of the model. In the meantime, I also have to figure out how to do 'hasOne' for an element that I have to do an additional query for.

[siebmanb]

One last trick : even if your model does not contain the right entries, most of the time the parameter "raw" in the callback response contains the data you are looking for. Dirty but efficient

[firekesti]

Hmm, what if I have a setup like this: a REST call gives me a list of 'entity' models which all work fine. But then, inside each 'entity' model is a 'body' link. The data for it is at '/entity/{id}/body' and I don't know if I should be using a hasOne for this or just some weird custom proxy stuff. The body should be part of the entity, but requires a separate call to be so.

[siebmanb]

I am not sure I understand. Are you asking if you should send all the entities together, or have a separate call to get the ones you want ?

[firekesti]

I'm using a RESTful api, so it does require another call to get certain elements. It's ok though, I found https://github.com/mhorner/RestModel and it looks like that will work a lot better for me. Thanks so much for your help though!

[siebmanb]

I believe doing another call is not always a bad idea : that way you don't get unnecessary data at first and the request stays light.

Good luck.