EventedConstructor has two constructors of different types about typings HOT 4 CLOSED

@msssk Can you please approve this PR - it is the same as the other with the hickup.

from typings.

@HeikoStudt where are you seeing this? I can't find it in dojo/typings:

new (...args: any[]): Evented & DeclareCreatedObject

Can you add an explanatory comment to the PR? It's an awkward scenario we are in where the existing typings are accurate, but don't work in practice. dojo/Evented is a plain JS constructor function, but it is intended to be used with dojo/_base/declare and declare supports mixing in plain JS constructors. Specifying Evented & _base.DeclareCreatedObject as the return type of the Evented constructor is not accurate and could actually allow invalid code to pass type-checking. I feel like that is a lesser danger than the problem of getting type errors when trying to use modules created with declare that include dojo/Evented though. So if you can add a comment to the PR I think we are good to go:

interface EventedConstructor extends _base.DeclareConstructor<Evented> {
	// While not technically accurate, it is necessary to add `_base.DeclareCreatedObject`
	// to avoid errors when mixing in Evented using declare
	// see https://github.com/dojo/typings/issues/170
	new (params?: Object): Evented & _base.DeclareCreatedObject;
}

from typings.

Probably, I made a substitution while putting it here. It is from dojo/1.11/_base.d.ts:

new (...args: any[]): T & DeclareCreatedObject;

I put the comment into the PR, thanks a lot!

from typings.

I landed the PR

from typings.