Jackie Li

> "One way of doing things" I agree with this. Although, I argue it shouldn't stop us from bringing in new things, if it's better. So what's the better way...

@a-h & @joerdav would you mind I starting with an experimental implementation? I went ahead and create a draft PR, got the first go at parser (with help from claude)....

> I think the hardest part will be the generator, because the HTML attributes would need to be mapped to the correct function args or struct fields, I had a...

> 🌶️ 🌶️ 🌶️ Please don't... If you want web component make web components. Jsx is not HTML and blurs the line too much and values easy over simple. Y'all...

it's almost 3 month since I started this proposal. After continue using it extensively I agree that introduce the new `` syntax is not particularly beneficial, I do find a...

OK, I admit there is a big problem with my approach: I didn't convert the templ URI to the Go URI, yet somehow it worked. It seems gopls is good...

I've been using it, works most of the time. But because it uses gopls to parse the templ files directly. It has quite a few broken cases. I'll redo it...

@a-h @joerdav I have implemented the said approach: use go source to find the symbols and map them back to templ source ranges. There are two issues I couldn't figure...

@joerdav @a-h the PR is ready as is. Please feel free to review and comment.

I'm been building lots of pages recently and really crave for this. It would make building reusable components even simpler. Consider this simpler example: We want a [dt](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/dt) and [dd](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/dd)...