[🐞] eslint rule qwik/use-method-usage does not account for renderHook testing utilities

[ianlet]

Which component is affected?

Qwik Runtime

Describe the bug

The qwik/use-method-usage rule currently allows use* calls only inside component$() or use*-named functions. This is too strict for testing utilities like renderHook, which wraps callbacks in component$() internally but isn't recognized by the linter.

// ✅ Works — but only when no arguments are needed
const { result } = await renderHook(useCounter);

// ❌ ESLint error — even though renderHook wraps this in component$() internally
const { result } = await renderHook(() => useCounter(10));

The workaround is to extract a use*-named wrapper function, which is unnecessary boilerplate:

function useCounterFrom10() {
  return useCounter(10);
}
const { result } = await renderHook(useCounterFrom10);

This affects at least two testing libraries:

• @noma.to/qwik-testing-library
• vitest-browser-qwik

Suggested fix: In useMethodUsage.ts, when the parent is an ArrowFunctionExpression or FunctionExpression inside a CallExpression, also allow callee names matching renderHook:

 if (parent.parent.type === 'CallExpression') {
   if (
     parent.parent.callee.type === 'Identifier' &&
-    parent.parent.callee.name === 'component$'
+    (parent.parent.callee.name === 'component$' ||
+     parent.parent.callee.name === 'renderHook')
   ) {
     return;
   }
 }

A more flexible approach would be making the list of allowed caller names configurable via rule options. Though that might allow qwik users to completely bypass this rule in situations where it should not.

Reproduction

ianlet/qwik-testing-library#92

Steps to reproduce

1. Install eslint-plugin-qwik
2. Write a test using renderHook(() => useSomeHook(args))
3. ESLint reports: Calling use* methods in wrong function.

System Info

N/A — this is about the ESLint rule logic, not runtime behavior

Additional Information

Related prior issue: #3787 (custom hooks were also incorrectly flagged)

[JerryWu1234]

@ianlet How do you think it that allows you pass whitelist
@wmertens

[wmertens]

I think this is making things very complicated. Just disable the rule where you know it's fine

[JerryWu1234]

I think this is making things very complicated. Just disable the rule where you know it's fine

@wmertens how to disable it?

Disable in Qwik eslint?

[ianlet]

@JerryWu1234 you can disable with // eslint-disable-line qwik/use-method-usage on the line that triggers the warning or with eslint-disable-next-line.

@wmertens without complicating things, do you think we could simply whitelist renderHook directly here? that would be beneficial for all testing libraries, though it might create a precedent and could start getting messy.

[JerryWu1234]

@wmertens allow user to pass a whitelist ?

[intellix]

We have this issue with vi.mock as well:

vi.mock('@myorg/utils-qwik', () => {
  return {
    useDevice: () => ({
      // oxlint-disable-next-line qwik/use-method-usage
      isMobile: useSignal(false),
    }),
  };
});

Maybe not a problem in v2 when we have createSignal?