You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you have a list output, the engine appears to use the first item to get the list schema. It does not validate hard-coded non-zero entries. This results in a validation failure when the output is created.
The engine should run infer on the other list items, then compare the type to ensure they match the first item.
The text was updated successfully, but these errors were encountered:
Also, it should be well-behaved if the list is empty (i.e., if there is nothing to use to get the list schema). Hopefully, this is basically a "fall-through" case, since, if the list is empty, there will also be nothing to which the engine needs to apply the schema which it cannot infer...but, it's worth testing.
Currently, if you have a list output, the engine appears to use the first item to get the list schema. It does not validate hard-coded non-zero entries. This results in a validation failure when the output is created.
The engine should run infer on the other list items, then compare the type to ensure they match the first item.
The text was updated successfully, but these errors were encountered: