Namespace/Module Incosistencies about ember-api-docs HOT 6 CLOSED

@Gaurav0 can you be specific about the "other data issues"?

from ember-api-docs.

@toddjordan So far, the only "other" data issues I have directly found are references to private methods and properties from public ones.

However, the app should never break regardless of any data issue. A reference to a namespace, module, class, property, method, or event that either doesn't exist or isn't currently visible according to toggles should result in a friendly error message.

from ember-api-docs.

ok, in 2.10, I clicked on every namespace and module. The only one that doesn't come up is the 'support' module. in 2.9 the glimmer module shows headings but no data

from ember-api-docs.

• ember-* is missing from each module (except ember)
• ember-extension-support is "support" in the new app (and loads blank)

new:

old:

• Ember.ApplicationInstance and Ember.Test load as Namespaces in other namespace details when in actuality they are Classes

• Ember shows up in Classes when it is actually a namespace

from ember-api-docs.

oddly, things are showing up as namespaces in the data that don't seem to be namespaces:

from ember-api-docs.

Ok, I think I understand somewhat what's happening.

1. modules in the left nav are defined from source code with @module or @submodule
2. the classes within a module are defined from any @class defined within a source file with the @module or @submodule label
3. the namespaces within a module are defined from any @namespace defined within a source file with the @module or @submodule label
4. the list of namespaces in the left nav are defined from source code with @static and @class

Where this gets us into trouble is something like Ember.ApplicationInstance is not listed @static, but it is listed as an @namespace for Ember.ApplicationInstance.BootOptions. Therefore Ember.ApplicationInstance shows up as a namespace under ember-application, but there is no link to it as a namespace. Question for this is, should classes listed as @namespace be @static? If not, should they really be an @namespace?

Another example is Ember shows up as a class under ember-metal because it has a @class, but it isn't listed as a class because it has an @static. the fix for this is not to list @class as a class for a module if it also has a @static

from ember-api-docs.