Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix intellisense for plugins with multiple @apply rules #8213

Merged
merged 2 commits into from Apr 27, 2022
Merged

Fix intellisense for plugins with multiple @apply rules #8213

merged 2 commits into from Apr 27, 2022

Commits on Apr 27, 2022

  1. Fix intellisense for plugins with multiple @apply rules 

    Intellisense uses `expandApplyAtRules` directly and doesn’t partition them. When a plugin registers components using something like `”@apply flex”: {}` more than once in the same component intellisense will break. This isn’t a problem for Tailwind CSS proper because we do rule partitioning. Given that Intellisense is using it directly though we shouldn’t outright break in the face of this situation even if the result isn’t 100% accurate (the source maps won’t be correct in this case).

Co-authored-by: psucoder <hungle.info@gmail.com>
    @thecrypticace @psucodervn
    thecrypticace and psucodervn committed Apr 27, 2022
    Copy the full SHA
    34af8c6 View commit details
    Browse the repository at this point in the history

  2. Update changelog

    @thecrypticace
    thecrypticace committed Apr 27, 2022
    Copy the full SHA
    5b40e25 View commit details
    Browse the repository at this point in the history