PR4: Model.load() broken

[stephen.friedrich]

This used to work in PR3 (with the config not wrapped of course):

    Ext.define('fitmob.model.Post', {        extend: 'Ext.data.Model',
       config: {
            idProperty: 'path',
            fields: ['path', 'parentUrl', 'pagingEnabled', 'content', 'nav'],
            proxy: {
                type: 'jsonp',
                url: 'http://www.fortis-it.de/cms/wp-admin/admin-ajax.php?action=fma_post'
            }
}
...
        Post.load(path, {
            scope: this,
            success: function (post) {
            }
       });

In PR4 this makes ST log the error "An Operation needs to have a model defined."
From looking at the sources I found a silly workaround:

        Post.load(path, {
            model: Post,
            scope: this,
            success: function (post) {
            }
       });

[Jamie Avins]

Thank you for the report and test case.

[karazy]

Thx for the workaround. I got the same error and my first thought was on having a wrong configuration.
But after I went with your workaround I'm seeing another error.

Uncaught TypeError: Cannot call method 'getId' of undefined

This error occurs in buildUrl method. The record object is undefined!

      
 buildUrl: function(request) {        var me        = this,
            operation = request.getOperation(),
            records   = operation.getRecords() || [],
            record    = records[0],
            format    = me.getFormat(),
            url       = me.getUrl(request),
            // @TODO: put back the operation id
            //id        = record ? record.getId() : operation.id,

            id        = record.getId();

[TommyMaintz]

Thanks for the report. This will be fixed in the beta.

[gubarez]

Something similar happens with store. I need to set the model when setting new proxy to a memory store, even though it has been set in the store config property. This happened after migrating from PR3 to PR4

myStore.setProxy({
            type:'memory',
        model: 'MyModel',
            data: quests,
            reader: {
                type: 'json',
                rootProperty: 'items'
            }
        });

[bweiler]

I ran into the same problem using operations.

		// Setup the read operation
		operation = new Ext.data.Operation({
			model: model, // ST4 code or documentation bug
			action: 'read'
		});

The model property was not required in PR3.

[TommyMaintz]

        Post.load(path, {
            scope: this,
            success: function (post) {
            }
       });

This has been fixed and will be part of the Beta.

myStore.setProxy({
            type:'memory',
        model: 'MyModel',
            data: quests,
            reader: {
                type: 'json',
                rootProperty: 'items'
            }
        });

This has also been made so you don't need to set the model in the config passed to setProxy().

In the case where you define an operation yourself manually, we require you to specify the Model that the operation is going to be handling. In the refactored data package, Operations take care of handling any type of response (update, destroy, read, create). In order to do this, they need to know which Model they are dealing with. I have updated the documentation to explain this.