You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and for the sake of possibility of creating semi "custom tags" I would want to get exposed isProps to be able to detect if props are provided as first argument to my function:
let isProps = (o) => protoOf(o ?? 0) === objProto
and then line in tagsNS would look like that:
let [props, ...children] = isProps(args[0]) ? args : [{}, ...args]
If no one using isProps minifier should inline it back, so no size impact.
The text was updated successfully, but these errors were encountered:
My current feeling is that since isProps function is quite easy to add on the client side (a just a couple lines of change) it probably doesn't have too much value to add another top-level function to VanJS.
btw: All top-level functions of VanJS are nested into a single van object when being exported. Thus that's not something minifier can trim off (this might be a design mistake of VanJS, but it's too late to fix).
btw: All top-level functions of VanJS are nested into a single van object when being exported. Thus that's not something minifier can trim off (this might be a design mistake of VanJS, but it's too late to fix).
There is this fragment in tagsNS:
and for the sake of possibility of creating semi "custom tags" I would want to get exposed isProps to be able to detect if props are provided as first argument to my function:
and then line in tagsNS would look like that:
If no one using isProps minifier should inline it back, so no size impact.
The text was updated successfully, but these errors were encountered: