syn-rsx

license: MIT

[syn]-powered parser for JSX-like [TokenStream]s, aka RSX. The parsed result is a nested Node structure, similar to the browser DOM, where node name and value are syn expressions to support building proc macros.

```rust use std::convert::TryFrom;

use eyre::bail; use quote::quote; use syn_rsx::{parse2, Node, NodeAttribute, NodeElement, NodeText};

// Create HTML TokenStream. let tokens = quote! { "hi" };

// Parse the tokens into a tree of Nodes. let nodes = parse2(tokens)?;

// Extract some specific nodes from the tree. let Node::Element(element) = &nodes[0] else { bail!("element") }; let Node::Attribute(attribute) = &element.attributes[0] else { bail!("attribute") }; let Node::Text(text) = &element.children[0] else { bail!("text") };

// Work with the nodes. asserteq!(element.name.tostring(), "hello"); asserteq!(attribute.key.tostring(), "world"); asserteq!(String::tryfrom(&text.value)?, "hi"); ```

You might want to check out the [html-to-string-macro example] as well.

Features

Not opinionated

Every tag or attribute name is valid

html <hello world />
Text nodes

Support for [unquoted text is planned].

```html

"String literal"

```
Node names separated by dash, colon or double colon

html <tag-name attribute-key="value" /> <tag:name attribute:key="value" /> <tag::name attribute::key="value" />
Node names with reserved keywords

html <input type="submit" />
Doctypes, Comments and Fragments

html <!DOCTYPE html>  <></>
Braced blocks are parsed as arbitrary Rust code

```html <{ let block = "in node name position"; } />

{ let block = "in node position"; }

```
Attribute values can be any valid syn expression without requiring braces

html <div key=some::value() />
Helpful error reporting out of the box

rust,no-run error: open tag has no corresponding close tag and is not self-closing --> examples/html-to-string-macro/tests/lib.rs:5:24 | 5 | html_to_string! { <div> }; | ^^^
Customization

A ParserConfig to customize parsing behavior is available, so if you have slightly different requirements for parsing and it's not yet customizable feel free to open an issue or pull request to extend the configuration.

One highlight with regards to customization is the transform_block configuration, which takes a closure that receives raw block content as ParseStream and lets you optionally convert it to a TokenStream. That makes it possible to have custom syntax in blocks. More details in [#9]