Patch for issue #32951

[spamshaker]

relaxed interface to fit with javascript behaviour

Fixes microsoft/TypeScript-DOM-lib-generator#1568

[typescript-bot]

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

[RyanCavanaugh]

Don't add a type parameter, just change the relevant occurrences of string.

The issue only mentions number, not boolean - please don't make unrequested changes

[DanielRosenwasser]

Apart from the generic addition, this change is incorrect. When values are iterated, they are always stringified. The only type that should be modified is for values that are allowed to be set.

[DanielRosenwasser]

I think that the change should actually happen on TypeScript-DOM-lib-generator.

[jakebailey]

This change is in a non-.generated. file, so I would think that it would be here (if at all).

[DanielRosenwasser]

But the correct fix and its relevant changes would be to generated files which originate from the generator.

[spamshaker]

@RyanCavanaugh @jakebailey @DanielRosenwasser Thanks for reviewing

But the correct fix and its relevant changes would be to generated files which originate from the generator.

That's what I thought at the beginning when I realised that the affected lib.dom.d.ts is not here.

Don't add a type parameter, just change the relevant occurrences of string.

The issue only mentions number, not boolean - please don't make unrequested changes

I am sorry for confusing, but the engines also transforms boolean to string "true"/"false" out of the box so I would suggest to update the original issue to handle all subject with the correct resolution.

I am going to use pnpm patch to handle it for now