Typescript issues

[greentore]

1. render is typed to only allow () => uhtml.Hole when the documentation hints pasing holes directly is allowed too.
2. html is typed to only allow primitive values or holes as values, which means inline event listeners like onclick=${handler} error.

[WebReflection]

what are you suggesting? I don't TS much so I might not fix this best

[greentore]

I took a closer look and realized 1 is a simple precedence error. Replacing () => Hole | Hole with (() => Hole) | Hole should fix it.
As for 2, I don't really understand the code well enough to suggest typings. The simplest solution would be to just use any / unknown in place of Value type (I believe that's how it was done in 3.x.x) to avoid false positives in user code.
Anyway, I managed to fix errors in my code by typing Value this way:

/**
 * @template T
 * @typedef {T | T[]} MaybeArray<T>
 */

/** @typedef {MaybeArray<null | undefined | string | number | boolean | Hole | ((...args: unknown[]) => unknown)>} Value */

but it's likely not bulletproof.

[WebReflection]

do you mind filing a PR? :D

[greentore]

Sure, I don't mind.
But first I want to know which approach you prefer: bailing out with unknown or trying to patch up Value type? Personally I'm leaning towards the former.

[WebReflection]

I don't care 🥳 I don't use TS and in this case it feels more like troubles than a feature, as the context is in the string surrounding the interpolation, and I am sure TS can't understand any of that, so it's OK to have any, actually that's probably for the best in general!

[WebReflection]

so, I went ahead and filed this MR #95

I think the function case is solved (even if for listeners is actually more like (event:Event) => void to me) but I am not sure what is the issue with Value ... it's currently specified as ...values:Value[] all over the place and it's never a maybe array of values, it's an always because of how tags work.