Results 1 to 5 of 5

Thread: The default request parameters of TreeStore

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTJS-6746 in 4.1.2.
  1. #1
    Sencha User
    Join Date
    Apr 2010
    Location
    China
    Posts
    43
    Vote Rating
    0
      0  

    Default The default request parameters of TreeStore

    Ext version tested:
    • Ext 4.1.1(GA)
    Browser versions tested against:
    • Chromium 18.0.1025.168 (Ubuntu 12.04)
    Description:
    • TreeStore - it will be two request parameters when it loading: node & id. id is superfluous, it may cause trouble to the service side.

  2. #2
    Sencha User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,029
    Vote Rating
    1367
      0  

    Default

    This is done on purpose so that the proxy can create the correct url if it's rest
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Frontend Engineer
    ________________
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:
    https://github.com/mitchellsimoens

  3. #3
    Sencha User evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    18,968
    Vote Rating
    931
      0  

    Default

    It would be nice to be able to disable it by setting the nodeParam to ''.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

  4. #4
    Sencha Premium Member woody's Avatar
    Join Date
    Mar 2008
    Posts
    8
    Vote Rating
    0
      0  

    Default It seems this is causing my Problem, too

    With 4.1.1., Ext.direct and TreeStore i've got the following id specific Problem

    My Settings seem to be more or less ignored
    nodeParam: 'parent_id',
    defaultRootProperty: 'group_id'

    node: {id: "57729" group_id: "1", parent_id: "0"}
    sends now
    Object {parent_id = "57729", id_catalog_group_system=31, id="57729" }
    or
    Object {parent_id = "1", id_catalog_group_system=31, id="1" }

    instead of
    Object {parent_id = "1", id_catalog_group_system=31}
    as in ExtJS 4.0.7
    Last edited by woody; 10 Jul 2012 at 1:46 AM. Reason: additional info
    Bernhard Werner

  5. #5
    Sencha Premium Member woody's Avatar
    Join Date
    Mar 2008
    Posts
    8
    Vote Rating
    0
      0  

    Default

    As I am using Ext.direct, I do not understand why there is sent an additional param "id", since ExtJS version 4.1.1.
    If it's a bugfix for Rest then it should be used only with Ext.data.Proxy.Rest only.

    Does someone know where the "id" is set anyhow.

    Code:
    beforeload: function(store, operation eOpts){
         console.log(operation.params); // Object {parent_id='1', id='1');
         operation.params = undefined;
         console.log(operation.params); // undefined;
    
    }
    So i thought the request would now content no data.
    There was sent Object{id='1'} don't know, and can't tell where that came in again.
    Bernhard Werner

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •