That’s how it has worked in previous versions. For example, if
float can’t convert the supplied value it reports
0. Zero is its implicit default value (a.k.a “fallback” value). If you wanted it to report
-1 instead of
0 all you needed to do is use explicitly indicate the desired default value with
The difference in the 2021.12.0 version will be that there will no implicit default value and you must explicitly specify it. So if you want the existing behavior, where it reports zero, you must indicate it with
The current version, 2021.10.0, just gives you a warning that
float is missing an explicit default value. It’s part of a two month grace period for everyone to update their templates in preparation for the December release when it becomes mandatory to supply a default value.
Basically, this makes everyone pay closer attention to what their template does when it encounters an unexpected value (like
unavailable or isn’t numeric in some other way).
FWIW, several of the templates I have helped users fix revealed fundamental flaws that were masked by the use of implicit defaults.