Skip to content

Slot props producing no-undef on <svelte:fragment> #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kjagiello opened this issue Apr 13, 2021 · 1 comment · Fixed by #147
Closed

Slot props producing no-undef on <svelte:fragment> #109

kjagiello opened this issue Apr 13, 2021 · 1 comment · Fixed by #147

Comments

@kjagiello
Copy link

Experimenting a bit with sveltekit and although the following code is working just fine, eslint gets confused and considers it invalid.

.svelte

  <svelte:fragment slot="loaded" let:stdout let:stderr let:render let:executionTime>
    <Playground {initialContent} {stdout} {stderr} {render} {executionTime} />
  </svelte:fragment>

eslint output

  39:35  error  'stdout' is not defined         no-undef
  39:44  error  'stderr' is not defined         no-undef
  39:53  error  'render' is not defined         no-undef
  39:62  error  'executionTime' is not defined  no-undef

Using eslint-plugin-svelte3 v3.1.2.

Let me know if I can assist with any more details.

@kjagiello
Copy link
Author

Just an update. It seems that this is related to the fact that I'm using a <svelte:fragment> here. Switching it out for, for example, a <div> suppresses the error.

@kjagiello kjagiello changed the title Slot props producing no-undef Slot props producing no-undef on <svelte:fragment> Apr 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant