We are using ExtJS 6.0.1 classic for our app and are attempting to generate documentation with it. Many references to Ext classes are spawning warnings for us:
Ext.util.Observable.addListener links to non-existing class
{@link Ext.container.Container#down} links to non-existing member
{@link Ext#getCmp Ext.getCmp()} links to non-existing member
{@link Ext#applyIf} links to non-existing member
... and more!
The ExtJS documentation is generating from the path "../ext/classic/classic/" but is missing a ton of classes.
Additionally, using "--builtin-classes": true, to attempt to mitigate issues with Ext's documentation linking has instead thrown a ton of errors on its own:
/usr/lib/ruby/gems/1.8/gems/jsduck-5.3.4/js-classes/Object.js:408: console.log links to non-existing class
/usr/lib/ruby/gems/1.8/gems/jsduck-5.3.4/js-classes/Object.js:345: this.name links to non-existing class
/usr/lib/ruby/gems/1.8/gems/jsduck-5.3.4/js-classes/Object.js:345: console.log links to non-existing class
... and much more!
Is this expected misbehavior for 6.x, or is there something weird going on we need to look for?
We are using ExtJS 6.0.1 classic for our app and are attempting to generate documentation with it. Many references to Ext classes are spawning warnings for us:
The ExtJS documentation is generating from the path "../ext/classic/classic/" but is missing a ton of classes.
Additionally, using "--builtin-classes": true, to attempt to mitigate issues with Ext's documentation linking has instead thrown a ton of errors on its own:
Is this expected misbehavior for 6.x, or is there something weird going on we need to look for?