Skip to content

using variables inside sass gives cssConflict warning #770

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
oviirup opened this issue Apr 27, 2023 · 0 comments · Fixed by #771
Closed

using variables inside sass gives cssConflict warning #770

oviirup opened this issue Apr 27, 2023 · 0 comments · Fixed by #771

Comments

@oviirup
Copy link

oviirup commented Apr 27, 2023

Techstack

Tailwind - 3.3.1
Tailwind IntelliSense - 0.9.11
next - 13.3.1
pnpm - 8.3.1

Context

I am using TailwindCSS in sass for my NextJS project. I needed some for loop to assign a variable to children like this

@for $index from 1 through 10
  li:nth-child(#{$index})
    --index: #{$index}

I have to use #{$index} otherwise this won't work though the loop works fine. it gives unnecessary warnings.

Please help me to fix it or at least disable the warnings.

relevant screenshot
image

The syntax highlighting is from syler.sass-indented extension

I can ignore the warning by disabling the lining in settings.json but this is not a permanent solution.

{
  "[sass]": {
    "tailwindCSS.lint.cssConflict": "ignore",
    "editor.defaultFormatter": "syler.sass-indented"
  },
}
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