Several enhancements

[fflorent]

• 6 (part 1) reduce the size of the plugin files taking advantages of inhenritance

• fix missing params for functions in union type (for instance : Ext.button.Button.handler was : fn()|string ; now : fn(button: +Ext.button.Button, e: +Ext.event.Event)|string)
• Add unit tests and completion tests with fixtures, update README.md

• 5 [ExtJS] Make completion work on class definition with inheritance

---

Some bugs:

• Can't auto-complete button argument of Ext.button.Button.handler(). I noticed the type in the hint of the function for this argument was "Ext.button.Button" despite what is specified in the definition (that is "+Ext.button.Button").
• Same for the second argument (the event). This time, the hint gives this type: ? instead of +Ext.event.Event
• Using !proto in !define objects introduces a weird regression I can't explain. For example, the type of Ext.grid.Panel.prototype.store is Ext_panel_Table_cfg.store (Ext_grid_Panel_cfg extends Ext_panel_Table_cfg). Wonder if that's a tern issue. Thoughts?

We may fix these bugs before merging or merge immediately if you think those are acceptable.

Florent

[angelozerr]

Great work @fflorent !

Using !proto in !define objects introduces a weird regression I can't explain.

Could you give me a sample?

[fflorent]

Could you give me a sample?

Here for example:

Same if you use new Ext.grid.Panel({sto<tab>}) syntax.

The Ext_some_Class_cfg type was introduced in PR #3 to allow auto-completion of config objects.

Florent