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
I had thought about this when I first wrote the library, then I concluded not to support this - the same way it is not supported in JSX. The reason is that knowing if there are properties or not would only be known at runtime.
In the end macroexpanded code would be significantly more convoluted and there would be additional runtime costs (which may or may not have an impact, we'd have to measure).
Having said this, I haven't made up my mind. I'm going to keep the issue open and think about it.
Currently the way around it is to define a component that directly embeds the properties.
I have this code:
is it possible to have
{prop1: "abc", prop2: def"}
as a variable?The text was updated successfully, but these errors were encountered: