docs/next/api/filter-api/

[utterances-bot]

Filters API | SquirrellyJS

Filters let you pass a value through functions.

https://squirrelly.js.org/docs/next/api/filter-api/

[littlejak20]

I get the following in the console if I do the same as described above.

"Cannot read property 'define' of undefined"

I know it's a beta. Could you tell me what the correct spelling is?

[littlejak20]

I found the mistake.
In the code snippet, "filters" is written in small letters.
A console.log output showed that "filters" must start with a capital F

[bgub]

Hi @littlejak20! Are you sure you're using Squirrelly v8 and not Squirrelly v7? You can install Squirrelly v8 with npm install squirrelly@beta. Since it is in beta, running npm install squirrelly downloads v7. Let me know if this solves your problem!

[littlejak20]

Sorry that I answer so late.
The problem has now been solved. I used an old beta from version 8. In Beta 0, the "F" from filter was still capitalized.

[bgub]

@littlejak20 glad to hear the problem was resolved 🎉

[ilanl]

I think Filter don't allow parameters as shown here, might be an issue

I'm using v8 + Typescript
export declare type FilterFunction = (str: string) => any | Promise<any>;

[bgub]

@ilanl filters can accept parameters, it looks like I just miswrote the type.

The problem is here. I think we should just be able to change:

export type FilterFunction = (str: string) => any | Promise<any>

to

export type FilterFunction = (str: string, ...filterParameters: any[]) => any | Promise<any>

or maybe even

export type FilterFunction = (str: any, ...filterParameters: any[]) => any | Promise<any>.

Would you be willing to submit a PR for this?

[ilanl]

For sure :) I'll submit the PR. And need to add this scenario to the tests

PR

I have a failure. Pls explain why. @nebrelbug