Need help with hasOne association

[jweber]

I'm trying to create a hasOne association on a model, and provide the associated data along with the parent model's data.

But I'm not sure how to configure the association, or how to access the associated data from an instance of the parent model. Could someone point me in the right direction?

As an example, with data like this:

{
  firstName: 'Joe',
  address: {
     street: 'Avenue L',
     city: 'Brooklyn'
  }
}

And models like this:

Ext.define('app.model.Person', {
	extend: 'Ext.data.Model',
	config: {
		fields: [
			{name: "firstName", type: "string"}
		],
		hasOne: {
			// this is the part I'm not sure about
			model: 'app.model.Address',
			name: 'address'
		},
		proxy: {
			type: 'ajax',
			...
			reader: {
				type: 'json'
			}
		}
	}
});

Ext.define('app.model.Address', {
	extend: 'Ext.data.Model',
	config: {
		fields: [
			{name: "street", type: "string"},
			{name: "city", type: "string"}
		]
	}
});

What would I put inside hasOne? And how would I access a Person's associated Address?

The intro to the API docs for HasOne is a little confusing. It seems to indicate that if X hasOne Y, the hasOne association should be configured on Y's model, not X's. Is this a typo? Also, the config names on the Ext.data.association.* classes (e.g. "associatedModel") are different from the ones used in almost every example (e.g. "model"). So it's not clear what maps to what.

[rdougan]

Yes, the documentation for that is wrong and will be updated in the next release. Sorry about that!

Your hasOne association should be on the person. The name field will automatically map to the field ont he record (so 'address' would use the 'address' field and create the 'getAddress' getter). If for some reason you want these to be different, you can use 'associationKey' to set the actual record field to be used.

Is your code working?

[jweber]

It didn't work as posted, although I've managed to cobble together something that works.

• The "name" config doesn't seem to do anything with HasOne. It seems like this only works with HasMany.
• Instead, I replaced it with two separate configs: "associationKey" for the field containing the associated data, and "getterName" for the getter function name:
  

  hasOne: {
  	model: 'app.model.Address',
  	associationKey: 'address',
  	getterName: 'getAddress'
  }

• In addition, I had to specify a proxy on the Address model. This seems strange, since I might want to use this model in other contexts:
  

  proxy: {
  	type: 'memory'
  }