Sorry if this is in the wrong place. It's related to JSX syntax highlighting (which yajs.vim doesn't support, so it's when used together with the mxw/vim-jsx plugin) but the offending syntax definition is part of this plugin. So think of it as furthering support for jsx plugins used in conjunction with yajs.vim [=
yajs.vim/syntax/javascript.vim:401:
syntax region javascriptParenObjectLiteral start=/(\_s*\ze{/ end=/)/ contains=javascriptObjectLiteral,@javascriptComments fold
The above definition causes the javascriptArrowFuncArg region to not be captured in the right place and instead be captured within the JSX, in the following example code. Simply commenting out the definition will fix this.
Sorry if this is in the wrong place. It's related to JSX syntax highlighting (which yajs.vim doesn't support, so it's when used together with the mxw/vim-jsx plugin) but the offending syntax definition is part of this plugin. So think of it as furthering support for jsx plugins used in conjunction with yajs.vim [=
yajs.vim/syntax/javascript.vim:401:
The above definition causes the javascriptArrowFuncArg region to not be captured in the right place and instead be captured within the JSX, in the following example code. Simply commenting out the definition will fix this.
Here's a screenshot of the faulty highlighting. The red text is what is captured as the javascriptArrowFuncArg region. https://a.pomf.cat/ziggfj.png
I'll try and make a pull request if I can figure out the vim regex. But you probably know this best. [=