• Bugfix (non-breaking change which fixes an issue)

Reported on the forum, if a TypedInput is initialised with a list of types where the first type in the list has no value (eg, timestamp), but the node property is a different type with value (eg str), then the TI gets the right type, but the value is blank.

This is happening because when the TI is initialised, it first sets the types, which causes the type to be primed as the first in the list (timestamp). It then applies the actual type (str), which is seen as a change in type from no-value to value - and it restores the 'old' value which is blank - overwriting the right value that was already there.

The fix is to not set the type when setting the types list if its part of the initialisation of the whole widget - because we know we'll be setting it to the right type a few lines later.