Open tliron opened 2 years ago
The problem appears an parsing special types, such as scalar-units.
The workaround is to use a primitive value. For example, instead of "1 GHz" for a scalar-unit.frequency, a "1e9" float value can be used.
It is unclear how this could be entirely fixed. The node filter, by design, can be applied to arbitrary node types and arbitrary capabilities.
The problem appears an parsing special types, such as scalar-units.
The workaround is to use a primitive value. For example, instead of "1 GHz" for a scalar-unit.frequency, a "1e9" float value can be used.
It is unclear how this could be entirely fixed. The node filter, by design, can be applied to arbitrary node types and arbitrary capabilities.