# syn-rsx
[![crates.io page](https://img.shields.io/crates/v/syn-rsx.svg)](https://crates.io/crates/syn-rsx)
[![docs.rs page](https://docs.rs/syn-rsx/badge.svg)](https://docs.rs/syn-rsx/)
[![codecov](https://codecov.io/gh/stoically/syn-rsx/branch/main/graph/badge.svg?token=2LMJ8YEV92)](https://codecov.io/gh/stoically/syn-rsx)
![build](https://github.com/stoically/syn-rsx/workflows/ci/badge.svg)
![license: MIT](https://img.shields.io/crates/l/syn-rsx.svg)
[syn](https://github.com/dtolnay/syn)-powered parser for JSX-like [TokenStreams](https://doc.rust-lang.org/proc_macro/struct.TokenStream.html), 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 quote::quote;
use syn_rsx::parse2;
let tokens = quote! { "hi" };
let nodes = parse2(tokens).unwrap();
assert_eq!(nodes[0].name_as_string().unwrap(), "hello");
assert_eq!(nodes[0].attributes[0].name_as_string().unwrap(), "world");
assert_eq!(nodes[0].children[0].value_as_string().unwrap(), "hi");
```
## Features
- **Not opinionated**
Every tag or attribute name is valid
```html
```
- **Text nodes**
```html
"String literal"
```
Support for [unquoted text is planned]
- **Node names separated by dash, colon or double colon**
```html
```
- **Node names with reserved keywords**
```html
```
- **Attribute values can be any valid syn expression without requiring braces**
```html
```
- **Doctypes, Comments and Fragments**
```html
<>>
```
- **Braced blocks are parsed as arbitrary Rust code**
```html
<{ let block = "in node name position"; } />
{ let block = "in node position"; }
```
- **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! {
};
| ^^^
```
- **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]
[`syn`]: /syn
[`TokenStream`]: https://doc.rust-lang.org/proc_macro/struct.TokenStream.html
[unquoted text is planned]: https://github.com/stoically/syn-rsx/issues/2
[#9]: https://github.com/stoically/syn-rsx/issues/9