Sebastian Fekete

@a-h Yes exactly. I try to extend the parser to allow using ```{% templ -->(d Data) for example for big templates to split it to partials for readability reasons.

same issue here

When I handcraft the destination type I can also set the optional fields manually as pointer. The only requirement is that the transcoder type fullfill one of the things: -...

I don't get it. Why this is a runtime option? The problem is when I assign a domain pg type (which is literally only a basic pg type with predefined...

Is there currently **ONE** existing js stack parser which can handle stacks which contains eval lines? I don't found any.

ah this issue already exists here. I created a duplicate in the bad repo: https://github.com/pganalyze/pg_query/issues/254

New idea: ## 13. Renderable Component Generate Render for Named type when no func name and param list passed: Example: ``` templ (c *Component) { ... } ``` should generate:...

New idea: ## 14. *(WIP!)* Omit empty string valued attribute Generate Render for Named type when no func name and param list passed: Example: ``` ``` should generate: ``` func...

New idea: ## 15. Use "//line" go prefix in generated file so that go directly points to the bad code in the template

For me 100% valuable because it allows to use pggen with pgx v5 in general. Maybe you should put batching behind an opt-in flag anyway because a lot of code...