Price Hiller

This is related to an issue I noticed in #201. We need to properly pick up the node pairs again.

Sorry for the *long* delay here, I'll take a look at a few of them. In the meantime though, PRs are *very* much welcome.

Hey @srcrip can you take a look at the related PR (https://github.com/windwp/nvim-ts-autotag/pull/206) and let me know if that works for Elixir? I have exactly *0* Elixir experience, so I need...

I've merged in #206, but I'm not sure how viable the alternative `heex` tags are to add here as we are using binds to set the tags. It would require...

Huh, now that's interesting. Good to know the per user custom config extension allowed a work around though -- a key reason for that refactor 😄. We're already defining `vue`...

> I’ll try with a minimal config and if I still have the bug I will reply here. A good minimal config is in our `tests/minimal_init.lua` for validating behavior.

> Seems like https://github.com/windwp/nvim-ts-autotag/issues/190 is related? Yeah, now playing around with it with the sample you screen shotted, I think #190 is related. When looking at the tree it appears...

Thanks for reaching out. Imo, I think the approach we're taking in `nvim-ts-autotag` makes things simple from the configuration side, but not robust. Imo, the best way to do this...

Go with whatever is easiest for you, if you have something working based on `nvim-ts-autotag` then a PR is preferred of course (just mark it as a draft), but if...

> [Link to the fork](https://github.com/roycrippen4/nvim-ts-autotag/blob/main-NEXT/lua/nvim-ts-autotag/possible-new-strategy.lua) > > I'm willing to spend some time attempting to integrate this if the interest is there and ya'll think the approach is promising. >...