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

[Zyphrax]

Perhaps not really a bug, but a limitation:

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

associations: {
      { type: 'hasMany', model: 'MyApp.model.Person' }
}

Could you perhaps allow AlternateClassNames there as well?
Would save a lot of useless prefixes.

[Jamie Avins]

Thank you for the report.

[Jacky Nguyen]

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.