[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/no-explicit-any] Unexpected any. Specify a different type.

ESLint errors detected.

analytics#lint:CI: command (/home/runner/_work/trieve/trieve/frontends/analytics) /tmp/yarn--1726696236707-0.5743994461427113/yarn run lint:CI exited (1)

Process completed with exit code 1.

The report-json file "${report}" could not be resolved.

ESLint errors detected.

[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'columns' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.

The following actions uses node12 which is deprecated and will be forced to run on node16: ataylorme/eslint-annotate-action@1.0.4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/