Added universal expressions (short form functions): $ex

[dbuezas]

$fn ({getFromConfig, xs, ...etc...}) => getFromConfig("title")
equivalent to
$f get("title")

(all other params also available)

[dbuezas]

What do you think about this?

• $fn is very explicit and easy to understand, but I find it too verbose. Having to state the parameters and whatnot is redundant.
• I'm considering this short form $f, that automatically adds this prelude:
  ({ getFromConfig, get, hass, vars, path, css_vars, xs, ys, statistics, states, meta })=>
• and also get is an alias of getFromConfig

I think that it's good to keep $fn not only to avoid further breaking changes, but also because it explains $f in a sense.

@FrnchFrgg @zanna-37 you've both been very critical and constructive, I'd really appreciate your opinions&thoughts on this

[dbuezas]

Here's the skynet's opinion:

$expr and $ex are really not bad. (I'll hold my urge to pick$jsex)

[dbuezas]

I used this a bit today and it is quite convenient, but I'll rename it to $ex, a "universal expression".

[FrnchFrgg]

Indeed, something like $ex or $expr is what I would recommend, since it corresponds to the expression part of a lambda function. I slightly prefer the longer form, but not much.

[FrnchFrgg]

Why do you check again for the type of value ?

[dbuezas]

To be extra sure?
Thanks, I fixed that now.

[dbuezas]

I slightly prefer the longer form, but not much.

I went with $ex partly to keep it short, but mostly because $fn also had 2 letters. I've been using it and it is quite convenient :)