This is because we work from top to bottom to grab the captures and then start work if our cursor is within the bounds of the captures rows.
solutions might be:
manipulate the order so the smallest captures get checked first. This would be tricky because we assign to filetype based on the proceeding capture from the template. Perhaps we capture the call_expression, order these by size then run the capture again to extract @lang and @template
description
when mapping an array of
a
to html elements inside another template the outer selection will always trigger the edit action.view code in context
This is because we work from top to bottom to grab the captures and then start work if our cursor is within the bounds of the captures rows.
solutions might be:
call_expression
, order these by size then run the capture again to extract@lang
and@template
https://github.com/aaaaargZombies/webcomponent-template-editor.nvim/blob/086c143151c3c71ccd55124e991d363a07a15879/lua/webcomponent-template-editor/init.lua#L90-L93