I've found problem with custom-components starting with style name, e.g. <styled-text>. The code you provide for detecting the surrounding tag does match here (https://github.com/posva/vim-vue/blob/master/syntax/vue.vim#L71). This is a problem because it breaks the syntax highlighting of the script block (as you can see in the screenshots).
Broken
Working
Can you please adapt the vueSurroundingTag to not mach custom components starting with style? I guess the intention of your code is to also be able to write something like <style scoped> and still match. However, it would need further adaption like including an optional group of one space with unlimited characters for each vueSurroundingTag. This would help to use styled-text as a component-name because it would neither match <style> nor <style scoped> (due to the missing space)
Hey!
I've found problem with custom-components starting with
style
name, e.g.<styled-text>
. The code you provide for detecting the surrounding tag does match here (https://github.com/posva/vim-vue/blob/master/syntax/vue.vim#L71). This is a problem because it breaks the syntax highlighting of the script block (as you can see in the screenshots).Can you please adapt the
vueSurroundingTag
to not mach custom components starting withstyle
? I guess the intention of your code is to also be able to write something like<style scoped>
and still match. However, it would need further adaption like including an optional group of one space with unlimited characters for each vueSurroundingTag. This would help to usestyled-text
as a component-name because it would neither match<style>
nor<style scoped>
(due to the missing space)