-
-
Notifications
You must be signed in to change notification settings - Fork 51
[Feature Request]: Add rainbow-parens Query Support for Vue #141
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
Comments
Can you please elaborate? I don't understand what exactly the problem is. |
![]() @HiPhish |
If I understand you correctly what you want is to highlight delimiters inside the |
Yes, exactly. Please help me implement this feature. |
I don't think I want to include this sort of thing with the plugin, but you can add it to your personal configuration. In your Neovim configuration (e.g.
This is a subset of the default query. Next in your rainbow delimiters configuration you need to tell the plugin to use your own custom query. vim.g.rainbow_delimiters = {
query = {
vue = 'rainbow-script'
},
} Or if you prefer Vim script let g:rainbow_delimiters = {
\ 'query': {
\ 'vue': 'rainbow-script'
\ },
\ } Note that your CSS will still be highlighted because it is not part of the Vue language. You will have to blacklist CSS if you don't want to highlight it. For more information see If more people want this type of query I can make it official, but until then you can add it to your configuration. |
Actually, now that I think about it you could leave the query completely empty. As it is right now the script tag is still getting highlighted, but maybe you don't want that.
|
Thanks for the help, I am happy with it now. |
I'm requesting the addition of rainbow-parens support specifically for script blocks in Vue files within the rainbow-delimiters.nvim plugin. Currently, while there are good highlights for other languages, Vue files do not have consistent parentheses highlighting for script tags, which can lead to readability issues when working with complex JavaScript code.
The text was updated successfully, but these errors were encountered: