Nested nodes with their own scope are not nested inside an each block scope

[DMartens]

Before You File a Bug Report Please Confirm You Have Done The Following...

• I'm using eslint-plugin-svelte. (*.svelte file linting does not work with the parser alone. You should also use eslint-plugin-svelte with it.)
• I'm sure the problem is a parser problem. (If you are not sure, search for the issue in eslint-plugin-svelte repo and open the issue in eslint-plugin-svelte repo if there is no solution.
• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.

What version of ESLint are you using?

8.41.0

What version of eslint-plugin-svelte and svelte-eslint-parser are you using?

• svelte-eslint-parser@0.29.0
• eslint-plugin-svelte@2.29.0

What did you do?

Configuration

-

{#each Array.from({ length: open ? count - 1 : count }, (_, i) => i) as item (item)}
{/each}

What did you expect to happen?

The function scope of the callback of Array.from is a child scope of the each scope.

What actually happened?

The callback scope is a sibling of the each scope (both inside the module scope).

Link to GitHub Repo with Minimal Reproducible Example

Reproducible by pasting the code into the playground (sorry I found no way to get a link with the code and tab already selected).

Additional comments

I did not try to find other svelte constructs where this bug may also happen.

[ota-meshi]

The callback scope is a sibling of the each scope (both inside the module scope).

I believe it is outputting the correct scopes.
What did you expect?

"childScopes": [
    {
      "type": "module",
      "childScopes": [
        {
          "type": "function",
          "variables": [
            {
              "name": "_",
            },
            {
              "name": "i",
            }
          ],
        },
        {
          "type": "function", // This scope is the one inside `{#each}...{/each}`.
          "variables": [
            {
              "name": "item",
            }
          ],
        }
      ],
    }
  ]

[github-actions]

This issue is is stale because it missing information and has been open for 60 days with no activity.

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂