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
I've been obfuscating the builder types in my application to clear the editor issue highlights. However, it seems that the root cause is the way the StructRowProxy type is created. It seems that instead of or | the type is created with {}&{}, and this causes the editor to complain.
Let's look at an example.
interfaceValueTypeextendsarrow.TypeMap{time: arrow.TimestampMillisecond,value: arrow.Float64,}typeValue={time: number,value: number,}constchildren: (arrow.Field<arrow.DateMillisecond>|arrow.Field<arrow.Float64>)[]=[newarrow.Field('time',newarrow.TimestampMillisecond()),newarrow.Field('value',newarrow.Float64()),]constvalueDataType: arrow.Struct<any>=newarrow.Struct<ValueType>(children)// forcing the Struct type here - without it the error message is the same and will just show <any> instead of <ValueType>constbuilder: arrow.StructBuilder<ValueType,null|undefined>=arrow.makeBuilder({type: valueDataType,nullValues: [null,undefined]})...constadd=(value: Value)=>builder.append(value)/*Argument of type 'Value' is not assignable to parameter of type 'StructRowProxy<ValueType>'. Type 'Value' is missing the following properties from type 'StructRow<ValueType>': toArray, toJSON, [kRowIndex], [kParent], [Symbol.iterator]*/
To prevent editor error highlights, I have to obfuscate the builder type.
I've been obfuscating the builder types in my application to clear the editor issue highlights. However, it seems that the root cause is the way the
StructRowProxy
type is created. It seems that instead of or|
the type is created with{}&{
}, and this causes the editor to complain.Let's look at an example.
To prevent editor error highlights, I have to obfuscate the builder type.
Reporter: Teodor Kostov
Note: This issue was originally created as ARROW-16750. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: