Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha User
    Join Date
    Mar 2009
    Posts
    240
    Vote Rating
    0
    r_honey is on a distinguished road

      0  

    Default Beta1 - NodeInterface constructor does not preserve custom field values

    Beta1 - NodeInterface constructor does not preserve custom field values


    Here's the code to test this:

    Code:
        Ext.define('NavigationModel', {
            extend: 'Ext.data.Model',
            fields: ['path', 'text', 'size', 'mime', 'extension']
        });
    
    var obj = new NavigationModel({text: 'Folder 1'});
    obj._data or obj.data does not seem to have a field called text after the above code executes.

  2. #2
    Sencha User Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    18
    Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough

      0  

    Default


    So when using the compat build, we get "fields is deprecated as a property directly on the Model prototype. Please put it inside the config object." We're going to leave the deprecation in for the sencha-touch-debug.js build in beta2 as this is causing a lot of confusion. Until then, you should switch to using the sencha-touch-all-compat.js build.

    Sencha Inc

    Jamie Avins

    @jamieavins

  3. #3
    Sencha User Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    18
    Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough Jamie Avins is a jewel in the rough

      0  

    Default


    I do apologize for the confusion, we're trying to find the right balance on the builds.

    Sencha Inc

    Jamie Avins

    @jamieavins

  4. #4
    Sencha User
    Join Date
    Mar 2009
    Posts
    240
    Vote Rating
    0
    r_honey is on a distinguished road

      0  

    Default


    No problem Jamies, thanks for the solution. And sorry for the false bug report.

Thread Participants: 1