@types/filter, @types/where, @types/chain having different definitions for callbacks than in the documentation

[szilike10]

I noticed when trying to execute any kind of filtering, the methods in the API have wring type definitions: () => DataFrame | Record<string, any> instead of {Function | Object} like in the JavaScript documentation. This makes impossible the filtering because the passed function defined in the documentation doesn't match the required definition.

Example usage in the documentation:
df.filter(row => row.get('column1') >= 3)

The errors I get:
Parameter 'row' implicitly has an 'any' type.
Type 'boolean' is not assignable to type 'DataFrame | Record<string, any>'.

As well as for the other example:
df.filter({'column2': 5, 'column1': 3}))

The error is:
Object literal may only specify known properties, and ''column2'' does not exist in type '() => DataFrame | Record<string, any>'.

Please inform me whether I am doing something wrong or the declarations in the @types are wrong.

[typescript-bot]

Hi, we could not find a reference to the types you are talking about in this discussion.
Please edit the title to include the name on npm inside square brackets.

E.g.

• "[@typescript/vfs] Does not x, y"
• "Missing x inside [node]"
• "[express] Broken support for template types"

By doing this, I can ping the folks who maintain the types you are referring to.