Kinds are lost during run-time

Jelly

First time posting here, hope someone can help me shed some light on the problem.

For Reference: http://jsfiddle.net/yr2t899f/

In 2.4 my application ran just fine and in 2.5+ it doesn't. The jsfiddle shows a nested namespace hierarchy, which is essentially how my application is structured. Once I instantiate one of the namespaced kinds, the others are lost.

Example kind structure:

A
A.B
A.B.C
A.B.D
A.B.E

If I instantiate A.B.C, A.B.D and A.B.E are undefined and removed from the A.B namespace. This happens regardless of which of the three I instantiate first.

Thanks,
Michael

rubenvreeken

It's a breaking change in 2. The reasoning behind the change was that you shouldn't be using the constructor of a kind as a namespace to define other kinds.

Some probably not too bad alternatives would be:

app.A
app.B
app.b.C
app.b.D
app.b.E

or

app.A
app.b.B
app.b.C
app.b.D
app.b.E

Jelly

Was this done as a side effect to some other feature that was implemented? Also, for future reference, where would this change have been documented? I was digging through changesets and the changelog trying to find it.

rubenvreeken

It was documented in the enyo migration guide, which for some reason is apparently not linked to in the official documentation:

https://github.com/enyojs/enyo-docs/blob/master/developer-guide/release-notes/migration-2.3-to-2.5.md

rubenvreeken

It appears from the migration guide that the change was intentional. Personally, I think the change is correct, using a constructor as namespace is just kind of weird when you think about it.

Jelly

Thanks so much, you've been extremely helpful. I appreciate the quick response.