add automation for Transferable

[mathe42]

This is a try to fix #1197. This might not the optimal solution!

I simply checked for all Interfaces if they have the Transferable attribute and added it to the addedItems object where it was defined before.

This is my first code-contribution here so there might be things that I missed.

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @saschanaz - if they write a comment saying "LGTM" then it will be merged.

[ExE-Boss]

I think that this should use a similar implementation to ArrayBufferLike¹:

/**
 * Allowed ArrayBuffer types for the buffer of an ArrayBufferView and related Typed Arrays.
 */
interface ArrayBufferTypes {
	ArrayBuffer: ArrayBuffer;
}
type ArrayBufferLike = ArrayBufferTypes[keyof ArrayBufferTypes];

Footnotes

1. https://github.com/microsoft/TypeScript/blob/03b12a6a45ca0dc043896160fd81060a980352d9/lib/lib.es5.d.ts#L1586-L1592 ↩

[mathe42]

That is a good solution for ArrayBufferLike as this can be extended (as it is a ES-Syntax-Thing) by the runtime (Browser, Node, Deno) with for example SharedArrayBuffer but Transferable is a Web-Feature that doesn't need to be extended. (Yes NodeJS and Deno adopt Transferable but they have theire own types independent from @types/web).

---

TL;DR: As this is nothing a user / runtime can extend. I prefere to keep it as it currently is.

[saschanaz]

This is an interesting approach! I thought I'd do it in emitter but this looks better than playing manually with strings.

LGTM

[github-actions]

Merging because @saschanaz is a code-owner of all the changes - thanks!

[HolgerJeromin]

Should this list be sorted to have a stable output?