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.

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

Not Working for Vue Transition Classes #1066

Open
ram-you opened this issue Oct 15, 2024 · 0 comments
Open

Not Working for Vue Transition Classes #1066

ram-you opened this issue Oct 15, 2024 · 0 comments

Comments

@ram-you
Copy link

ram-you commented Oct 15, 2024

After upgrading to version 0.12.0 (and above), auto-completion within Vue transition components is no longer functioning as expected. This includes attributes such as enter-active-class, leave-active-class, enter-from-class, and leave-to-class.

   <transition
     enter-active-class="transition-transform origin-right duration-300 ease-out"
     enter-from-class="scale-x-0 -z-1"
     enter-to-class="scale-x-100 z-10"
     leave-active-class="transition-transform duration-150 ease-in"
     leave-from-class="scale-x-100 z-10"
     leave-to-class="scale-x-0 -z-1"
     appear>
   </transition>

In version 0.10.5, the following regex pattern worked for class auto-completion:

"tailwindCSS.experimental.classRegex": [
  "(?:enter|enter-active|enter-from|enter-to|leave|leave-active|leave-from|leave-to)-class=\"([^\"]*)\"",
  "(?:enter|enter-active|enter-from|enter-to|leave|leave-active|leave-from|leave-to|entered)=\"([^\"]*)\""
]
  • I attempted various configurations in the .vscode/settings.json file, including different regex patterns for the tailwindCSS.experimental.classRegex setting, but the issue persists.
  • I tested with a simpler regex pattern: "\\-class\\s*=\\s*\"([^\"]*)\", which still did not yield any results.
  • Disabled other extensions that may conflict, including Vetur, but auto-completion remains inactive.
  • Created a new Vue project with a minimal setup to eliminate project-specific issues, but the problem persists in this clean environment.
  • Downgraded to version 0.10.5 of the extension, which restored the expected functionality.

Thank you.

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

No branches or pull requests

1 participant