V5.3.0: Custom widgets and filter operator names must now contain a period

#1

I’ve made a small change to the v5.3.0 prerelease which is not fully backwards compatible with previous versions of the prerelease.

The names of custom widgets and filter operator must now contain a period. (Custom widget names continue to also require a dollar sign as the first character).

For example:

\widget $my.custom.widget()
...
\end

<$my.custom.widget>
...
</$my.custom.widget>

And:

\function my.custom.function(a)
...
\end

<$text text={{{ [my.custom.function[22]] }}}/>

Previously, custom widget names had to start with a double dollar sign, and custom filter operator names had to start with a period.

This change is intended to makes things more consistent. See the discussion on GitHub for details.

5 Likes
Final Checks Before Release of v5.3.0
#2

this makes a lot of sense, ensuring backwards compatibility by never making official widgets / filter operators that contain periods. thanks!

#3

Thank you Jeremy!
The one dollar sign is much more readable than two dollar signs! and the dot shout, the widget or operator is a user defined one.
UDF → user defined function
UDW → user defined widget

2 Likes