cabboose

This isn't an issue in `Solid-js`, as components are just function calls. For me personally, I think this is correct. Better that component rendering is explicit rather than implicit and...

An operator or function could be introduced which forces a function call that outputs a `JSX.Element` to compile as a tag. You could then create a helper that combines that...

Indeed, but I think Freymauer wants to avoid explicit decoration of a function that should be compiled as a tag. To clarify though, I am 100% for explicit decoration over...

## `__SPREAD_PROPERTY__` Permits a value to be wrapped in obj spread syntax within JSX elements within the already defined property key,value schema. ie, a property key,value pair of `"__SPREAD_PROPERTY__", myProperties`...

@alfonsogarciacaro This PR is ready with tests; I will be able to produce tests for #4037 after this is merged as the tests will not work with #4037 (so I...

As it currently stands, this is to enable plugins (specifically [Oxpecker.Solid](https://github.com/Lanayx/Oxpecker/pull/51)) to provide this functionality via some other API. There is no *easier* way to produce these type of attributes...

I'm not at all against that ideology. To allow this same functionality to be used in the std Fable JSX seems doable. #### Spread Prop ```fs [] let Button (prop...

> ### Bool prop > Type aliases disappear in Fable AST, but if this general JSX behavior, we can just skip printing the value if it's a `true` literal (and...

I'm a bit stuck at this point, I'm passing the attributes down the transformation tree, but I'm not sure how to approach it from here. Is there some way to...

I had a thought, but wouldn't this kind of work? It's more future proof. Passing an empty string `""` would already compile and be invalid JSX. Might as well leverage...