Moved the Widget V2 test widgets to under the UizeSite.Widgets namespace to keep things in the Uize namespace relatively clean while this development work occurs.
The Uize.resolveTransformer method now supports the transformer being specified as an array, where the value being transformed will be coerced to a number and used as an index to look up the transformed value from the array.
Don't need this console.log anymore.
Don't need to access the DOM in the getHtml method unless the html state property is set to true (the magical behavior for in-HTML templates), and this was actually causing problems for some new widget tests I was writing, because the null value was being cached in the node cache when getHtml was being called because a widget's HTML wasn't already in the page and needed to be added to the document.
The V2 widget base class now supports state to CSS bindings in a declarative mechanism.
Created a V2 version of the button widget to start testing the principles of HTML and CSS encapsulation for V2 widgets, and also the new state to CSS binding mechanism.
Let's start fresh with formatting of CSS for the V2 widgets.
Now that we have V2 widgets being created, we can restore the old widgets to subclassing Uize.Widget, rather than the V2 subclass.