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

      0  

    Default Can't use AlternateClassName in associations (ST2-RC2)

    Can't use AlternateClassName in associations (ST2-RC2)


    Perhaps not really a bug, but a limitation:

    In associations I can't use the AlternateClassName, but I have to use the actual ClassName.

    Code:
    associations: {
          { type: 'hasMany', model: 'MyApp.model.Person' }
    }
    Could you perhaps allow AlternateClassNames there as well?
    Would save a lot of useless prefixes.

  2. #2
    Sencha - Sencha Touch Dev Team Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    21
    Jamie Avins is a jewel in the rough 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


    Thank you for the report.

    Sencha Inc

    Jamie Avins

    @jamieavins

  3. #3
    Sencha - Sencha Touch Dev Team Jacky Nguyen's Avatar
    Join Date
    Jul 2009
    Location
    Palo Alto, California
    Posts
    469
    Vote Rating
    14
    Jacky Nguyen has a spectacular aura about Jacky Nguyen has a spectacular aura about

      0  

    Default


    Without the model class being loaded upfront, there's no automatic way to having the mapping between an alternateClassName to the actual class name.

    Alternate class name is primarily meant for backwards compatibility, you shouldn't use it for naming convenience. Full class name referencing of all custom classes is always recommended.
    Sencha Touch Lead Architect