-
Notifications
You must be signed in to change notification settings - Fork 332
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
Unrecognised Vue Directive in Jet Brains IDE when using floating-vue directive #991
Comments
Would having TypeScript types help solve this? I'm not really familiar with Jetbrains IDEs |
@Akryum I think it would as normally the suggested solution for these sort of issues is to install types. You can see package like bootstrap-vue auto generate it: https://github.com/bootstrap-vue/bootstrap-vue/blob/dev/package.json#L16C11-L16C11 |
Also a bump for me, indeed it would be good to generate + publish this. Floating-vue is currently leading in the popper/dropdown/tooltip market in vue. Please add this. |
This issue might not be directly a
FloatingVue
issue but I feel like it is related to at least raise it and hopefully get some pointers on resolving it.When using
FloatingVue
with the install plugin option and then using it within the components, we get an warningUnrecognized Vue directive
on all the JetBrains IDE (PHPStorm, WebStorm, Ultimate)..
If we use the directive method of installation, then that warning is not displayed.
This issue has been logged with YouTrack and has a specific example with
FloatingVue
(https://youtrack.jetbrains.com/issue/WEB-52855/Vue-3-Custom-Directives-not-being-picked-up-by-IDE-if-defined-on-App-object#focus=Comments-27-6228126.0-0).The solution suggested seems to be the library to provide a WebType definition (https://blog.jetbrains.com/webstorm/2021/01/web-types/) or a temporary fix to not show the error on the JetBrains IDE by creating a web-types file to hide all warnings for the directive. I have created an added the
web-types
to thepackage.json
which hides the warning but I was wondering if there was a better solution that might even provide autocomplete when using the directive?The text was updated successfully, but these errors were encountered: