Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-fable-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION unused-class-members FP: methods called only from Svelte <template>…

  1. User

    ISSUE DESCRIPTION

    unused-class-members FP: methods called only from Svelte member expressions False positive on 2.84.0. Class methods called only from a Svelte <template> via a member expression (for example resultState.pin(...) in markup) are reported as unused-class-member. Fallow tracks template-visible identifiers but not member-expression method calls on a bound instance inside Svelte markup.

    Repro (2.84.0): asciimoo/hister. ResultState.onOpen, .pin, .updateLabel, and .addSkipRule are each invoked from .svelte templates (resultState.pin(...) in ResultActionsMenu.svelte) yet reported unused. The repo currently sets rules.unused-class-members: "off" to work around it.

    Expected: credit a method called as <local>.<method>(...) inside a Svelte <template> when <local> resolves to an instance of the class, parallel to the existing Vue/Angular template member-access tracking.

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /fallow, current file: none) bash-$

  2. Claude Assistant

    The basic mechanism seems to exist (there's even a fixture with counter.bump() in a Svelte template). Let me build the CLI and construct repro variants to find what breaks.

  3. Claude Assistant

    Local instantiation works. Now test the imported-instance variant:

  4. Claude Assistant

    The typed $props() destructure is the failing case. Let me test a couple more variants to scope the fix:

  5. Claude Assistant

    Now add calls in into_module_info and merge_into, plus a recording helper:

  6. Claude Assistant

    Now verify a truly-unused method is still flagged (no over-crediting):

  7. Claude Assistant

    Also verify the same pattern works in plain .ts scripts (finalize path):

  8. Claude Assistant

    Now run existing tests:

  9. Claude Assistant

    Pre-existing environment failure (running as root defeats read-only dir). Unrelated. Now check fmt and clippy:

  10. Claude Assistant

    Let me test renamed and nested destructure edge cases:

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.