senchalabs/jsduck — Issue #107: Lack of Ext JS 4 Sandbox support
Author: chge
Created: 2011-12-15 07:40:14+00:00
State: open

It'll be cool if JSDuck could understand that ExtJS 4 is in sandbox mode.

We have an application with a lot of legacy Ext JS code, thus we need to use sandboxing and have to use ```Ext4``` namespace root for 4th version. In this situation, auto-documenting (```extend, mixins, requires, singleton...```) doesn't work. And it's not a good idea to document all custom classes by hands using whole set of "@" annotations instead of built-in capabilities. Now we are have to temporarily auto-replace ```Ext4.define``` to ```Ext.define``` in whole project when building docs.

Are there ways to tell to JSDuck that "Ext4 is Ext" with one comment or command-line flag?