You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression
[ ] Bug report
[X] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
classA{constructor(a: string){}}classB{constructor(b: number){}}classCextendsIntersectionType(A,B){constructor(){super();// <- hint `Type(...args: any[]): A & B` shown here}}
I've checked the source code, found that for each mapped type, a new class with no constructor is created, and "base"(?) classes's constructor are never called.
Expected behavior
Add a new type
exporttypeMappedType<T>=new()=>T
as return type of mapped types.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
This can clearify the constuctor parameter of mapped types, implies that constructors of base classes will not be called.
Environment
Nest version: 7.1.3
For Tooling issues:
- Node version: XX
- Platform:
Others:
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
I've checked the source code, found that for each mapped type, a new class with no constructor is created, and "base"(?) classes's constructor are never called.
Expected behavior
Add a new type
as return type of mapped types.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
This can clearify the constuctor parameter of mapped types, implies that constructors of base classes will not be called.
Environment
The text was updated successfully, but these errors were encountered: