handlebars-rust VS sqlparser-rs

handlebars to create the HTML templates of all the built-in components

handlebars-rust, based on Handlebars

Handlebars/guide/#what-is-handlebars)

filling out templates inside files using Handlerbars

Would Handlebars-Rust be good for parsing non-Rust files? Or is there another templating engine built in Rust that I should use?

I am learning Rust currently, so to improve my skills, I am considering using its Handlebars implementation.

If you paid attention to the function code above, it might have occurred to you that the assets we serve don't have to be completely static. For example we could instead embed a handlebars template or similar & render it with the handlebars crate, allowing us "semi-dynamic" content for lack of a better name.

Tera is a templating engine, inspired by Jinja2 and Django. There are other options like handlerbars and askama, but in this case I prefer to use tera because I'm familiarized with the syntax.

This weekend I learned some unfamiliar behaviors with the way Handlebars handles nested variable scopes. I typically use Handlebars via the handlebars-rust implementation which aims to maintain nearly one to one compatibility with the JavaScript implementation. They have block scope helpers such as #each and #with, both of which create an inner scope for variable resolution. Unfortunately, the syntax can be quite unintuitive for accessing outer scope once in those nested scopes.

I have been tweaking and fixing issues with newline stripping feature for handlebars: https://github.com/sunng87/handlebars-rust/pull/448/files

sqlparser to parse SQL queries and detect variable bindings

So to start with this, I looked into SQL parsing and found this library https://github.com/sqlparser-rs/sqlparser-rs

We switched to an open source alternative, the rust-based sqlparser-rs library, contributing a few updates for the BigQuery dialect.

I have experience with sqlparser-rs (for my sqlpage project), but it does not track the source code location of the parsed data structures (yet).

It uses https://github.com/sqlparser-rs/sqlparser-rs as the parser and lexer. The binder, planner, optimizer and executor are in Python. The optimizer stage only works on the logical plan and the rules are heuristic only.

That code could be copied directly from some real-world examples - sqlparser-rs code looks pretty much exactly the same.

https://github.com/sqlparser-rs/sqlparser-rs

Also neat to find the SQL parser library they use.