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
nativeTags is hard to use #2165
Comments
I am using take over mode. |
If you see the change, If you really need the long list, you can modify the default long list {
"vueCompilerOptions": {
"plugins": ["./your-plugin"]
}
} import { VueLanguagePlugin } from '../types';
const plugin: VueLanguagePlugin = (cxt) => {
cxt.vueCompilerOptions.nativeTags = cxt.vueCompilerOptions.nativeTags.filter(...);
return { version: 1 };
};
export = plugin; |
Ah I just miss that change. Thanks for pointing it out and thanks again for your great work! ❤ |
Hi. Thanks for your work first!
I am
@uni-helper/uni-app-types
author and the package is providinguni-app
elements types. I notice that v1.0.10 addsnativeTags
and removesexperimentalRuntimeMode
. I also see #2065.I think
nativeTags
is hard to use. With #2065 example, as shown below.It doesn't parse the correct types of
view
andscroll-view
, but parse the other elements.To accurately parse types, I think I need to set a long
nativeTags
, which includes https://github.com/johnsoncodehk/volar/blob/master/vue-language-tools/vue-language-core/src/utils/ts.ts#L121-L128 elements and excludeuni-app
elements. Here I excludeview
,text
,progress
and so on.Can I have a better way to specify
uni-app
elements without such a long list?The text was updated successfully, but these errors were encountered: