fix(linter/no-invalid-fetch-options): ignore non static method

[camc314]

fixes #13010

[camc314]

• fix(linter/no-invalid-fetch-options): ignore non static method #14806 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull Request Overview

This PR fixes issue #13010 by improving the handling of non-static method properties in the no-invalid-fetch-options linter rule. When a method name cannot be resolved (e.g., when it references an external variable), the rule now marks it as unknown rather than continuing with potentially incorrect analysis.

Key Changes:

• Added fallback behavior to set method_name to UNKNOWN_METHOD_NAME when a symbol cannot be resolved
• Added test case covering the scenario where method options are passed as variables

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[graphite-app]

Merge activity

• Oct 20, 10:24 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Oct 20, 10:28 AM UTC: Merged by the Graphite merge queue.

[codspeed-hq]

CodSpeed Performance Report

Merging #14806 will not alter performance

_{Comparing c/10-20-fix_linter_no-invalid-fetch-options_ignore_non_static_method (dc03c3a) with main (8b02074)¹}

Summary

✅ 4 untouched
⏩ 33 skipped²

Footnotes

1. No successful run was found on main (dc03c3a) during the generation of this report, so 8b02074 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 33 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩