fix(runtime): narrow onInput & onCapture event types

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Unit tests (npm test) were run locally and passed
• E2E Tests (npm run test.karma.prod) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

In order to remove the type casting for the ionInput event types, the emitted type for DomAttributes will need to match InputEvent.

GitHub Issue Number: ionic-team/ionic-framework#24111

What is the new behavior?

Libraries/applications using Stencil, will have the input event strongly typed to InputEvent instead of the general Event type.

Does this introduce a breaking change?

• Yes
• No

Testing

Other information

[rwaskiewicz]

Thanks!

This change makes sense to me. Since it alters our public API by expecting non-nullable fields on for events:

interface UIEvent extends Event {
    readonly detail: number;
    readonly view: Window | null;
    /** @deprecated */
    readonly which: number;
}

interface InputEvent extends UIEvent {
    readonly data: string | null;
    readonly inputType: string; 
    readonly isComposing: boolean;
}

I'm a tad concerned about breaking changes. I would suspect most folks are using type assertions to trick the compiler, but I can't say for certain that's what's happening. Out of abundance of caution, I'm going to merge this into the v3 branch.

Thanks again!

[rwaskiewicz]

Gotta fix a small configuration bug for CI to run, hold tight!