senchalabs/jsduck — Issue #111: Ext.emptyFn as a method, rather than property
Author: jeffthink
Created: 2011-12-20 13:41:15+00:00
State: open

First of all, thanks for this great tool - it has made our codebase much more understandable and manageable.

I may be wrong here, but to me, it makes sense to treat a property that's initially set as an Ext.emptyFn to be a method, not a property. Even with the ```@type Function``` tag, it's still somewhat confusing that this method is not in the methods list. We generally use Ext.EmptyFn for methods that can be overridden by children classes, but if not, no harm done - maybe that's not a typical usecase?

Also, in this case, we'd ideally want to have docs for each of these methods in the parent class, then the child would inherit those + be able to add any custom docs on top of that, such as:

```
/**
* Does some child specific stuff
*
* @inheritdoc
*/
overriddenFn: function(){...}
```

The above currently doesn't work, and I'm thinking that it's because the parent's method is considered a property, not a method.