bug: @Event type is incorrectly generated when it emits it as an array

[scaljeri]

Prerequisites

• [X] I have read the Contributing Guidelines.
• [X] I agree to follow the Code of Conduct.
• [X] I have searched for existing issues that already report this problem, without success.

Stencil Version

2.19.2

Stencil Framework Output Target

Angular

Stencil Framework Output Target Version

0.4.0

Current Behavior

If a Stencil Components contains

   myEvent: EventEmitter<CustomEvent<IMyData>>;
   myEventArr: EventEmitter<CustomEvent<IMyData[]>>;  // <-- This one goes wrong!!!!!

The generated output in the proxies.ts file is now as follows

import type { IMyData as IMyFooIMyData } from '@web-components/dist/components';
export declare interface MyFoo extends Components.MyFoo {
    myEvent: EventEmitter<CustomEvent<IMyFooIMyData>>;
    myEventArr: EventEmitter<CustomEvent<IMyData[]>>;
}

So, as soon as the event emits an array of some type, the generated code uses the original name of the interface and not the mapped type.

Expected Behavior

For the generated code, it should have generated

    myEventArr: EventEmitter<CustomEvent<IMyFooIMyData[]>>;

Steps to Reproduce

See above

Code Reproduction URL

https://github.com/scaljeri/stenciljs-angular-bug.git

Additional Information

No response

[scaljeri]

Any progress on this issue?

[jdevillard]

Hello have you tried with the v 0.5.0 ?

[tfrijsewijk]

@scaljeri Have you seen my issue https://github.com/ionic-team/stencil-ds-output-targets/issues/283 ? Could you try

myEventArr: EventEmitter<CustomEvent<Array<IMyData>>>; // Instead of EventEmitter<CustomEvent<IMyData[]>>