[−][src]Macro format_xml::xml

macro_rules! xml {
    ($($tt:tt)*) => { ... };
}

Template XML-like.

Compiles down to a single format_args! invocation.

Safety

Arguments are not escaped by default! Use the escape! macro to format and html escape its contents.

Examples

Basic usage

let point = (20, 30);
let name = "World";

xml! {
	<svg width="200" height="200">
		<line x1="0" y1="0" x2={point.0} y2={point.1} stroke="black" stroke-width="2" />
		<text x={point.1} y={point.0}>"Hello '" {name} "'!"</text>
	</svg>
}.to_string()

The resulting string is <svg width="200" height="200"><line x1="0" y1="0" x2="20" y2="30" stroke="black" stroke-width="2" /><text x="30" y="20">Hello 'World!'</text></svg>.

Note how the expression values to be formatted are inlined in the formatting braces.

Formatting specifiers

let value = 42;

xml! {
	<span data-value={value}>{value;#x?}</span>
}.to_string()

The resulting string is <span data-value="42">0x2a</span>.

Due to limitations of declarative macros, a semicolon is used to separate the value from the formatting specifiers. The rules for the specifiers are exactly the same as the standard library of Rust.

Composition

fn compose(f: &mut std::fmt::Formatter, a: i32) -> std::fmt::Result {
	f.write_fmt(xml! {
		<span>{a}</span>
	})
}

xml! {
	<p>|f| { compose(f, 42) }</p>
}.to_string()

The resulting string is <p><span>42</span></p>.

Closure syntax allows capturing of the underlying formatter like you would when writing a custom fmt trait. This enables to compose the final XML from reusable subtemplates.

Supported tags

xml! {
	<!doctype html>
	<?xml version="1.0" encoding="UTF-8"?>
	<tag-name></tag-name>
	<ns:self-closing-tag />
	<!-- "comment" -->
	<![CDATA["cdata"]]>
}.to_string()

The resulting string is <!doctype html><?xml version="1.0" encoding="UTF-8"?><tag-name></tag-name><ns:self-closing-tag /><![CDATA[cdata]]>.

Control flow

let switch = true;
let opt = Some("World");
let result: Result<f32, i32> = Err(13);

xml! {
	if let Some(name) = (opt) {
		<h1>"Hello " {name}</h1>
	}
	else if (switch) {
		<h1>"Hello User"</h1>
	}
	if (switch) {
		match (result) {
			Ok(f) => { <i>{f}</i> }
			Err(i) => { <b>{i}</b> }
		}
		<ul>
		for i in (1..=5) {
			let times_five = i * 5;
			<li>{i}"*5="{times_five}</li>
		}
		</ul>
	}
	else {
		<p>"No contents"</p>
	}
}.to_string()

The resulting string is <h1>Hello World</h1><b>13</b><ul><li>1*5=5</li><li>2*5=10</li><li>3*5=15</li><li>4*5=20</li><li>5*5=25</li></ul>.

Control flow are currently only supported outside tags. They are not supported in attributes. The expressions for if and for must be surrounded with parentheses due to declarative macro limitations.

Specialised attribute syntax

let has_a = true;
let has_b = false;
let make_red = true;

xml! {
	<div class=["class-a": has_a, "class-b": has_b]>
		<span style=["color: red;": make_red]></span>
		<p data-attr=("has_a:"{has_a}",has_b:"{has_b})></p>
		<p data-fmt=|f| { f.write_str(if make_red { "MAKE_RED" } else { "" }) }></p>
	</div>
}.to_string()

The resulting string is <div class="class-a "><span style="color: red; "></span><p data-attr="has_a:true,has_b:false"></p><p data-fmt="MAKE_RED"></p></div>.

Dedicated syntax for fixed set of space delimited attribute values where each element can be conditionally included. This is specifically designed to work with the style and class attributes of html.

If attributes require more advanced formatting, the template! syntax is available by wrapping the value in parentheses. For even more power closure syntax is available to write custom formatting code. The curly braces are required.

Limitations

This crate is implemented with declarative macros. Because of this, there are various limitations:

It is not possible to check whether tags are closed by the appropriate closing tag. This crate will happily accept <open></close>. It does enforce more simple lexical rules such as rejecting </tag/>.
Escaping of &<>"' is not automatic. You can trivially break the structure by including these characters in either the formatting string or formatted values. Avoid untrusted input!
The formatting specifiers are separated from its value by a semicolon instead of a colon.
The compiler may complain about macro expansion recursion limit being reached, simply apply the suggested fix and increase the limit. This crate implements a 'tt muncher' which are known to hit these limits.
Text nodes must be valid Rust literals. Bare words are not supported.
Braces must be escaped, eg. "{{ }}" results in a single set of { }.