1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

use proc_macro::TokenStream;
use quote::{quote, quote_spanned, ToTokens};
use syn::spanned::Spanned;
use syn::{
    parse::{Parse, ParseStream},
    Signature,
};
use syn::{
    parse_macro_input, Attribute, Block, FnArg, Ident, Item, ItemFn, ReturnType, Type, Visibility,
};

mod fc;
mod htm;
mod ifmt;
// mod styles;

/// The html! macro makes it easy for developers to write jsx-style markup in their components.
/// We aim to keep functional parity with html templates.
#[proc_macro]
pub fn html(s: TokenStream) -> TokenStream {
    let html: htm::HtmlRender = match syn::parse(s) {
        Ok(s) => s,
        Err(e) => return e.to_compile_error().into(),
    };
    html.to_token_stream().into()
}

/// Label a function or static closure as a functional component.
/// This macro reduces the need to create a separate properties struct.
#[proc_macro_attribute]
pub fn fc(attr: TokenStream, item: TokenStream) -> TokenStream {
    use fc::{function_component_impl, FunctionComponent};

    let item = parse_macro_input!(item as FunctionComponent);

    function_component_impl(item)
        .unwrap_or_else(|err| err.to_compile_error())
        .into()

    // function_component_impl(attr, item)
    // let attr = parse_macro_input!(attr as FunctionComponentName);
}

#[proc_macro]
pub fn format_args_f(input: TokenStream) -> TokenStream {
    use ifmt::*;

    let item = parse_macro_input!(input as IfmtInput);

    // #[allow(unused)]
    // const FUNCTION_NAME: &str = "format_args_f";

    // debug_input!(&input);

    ifmt::format_args_f_impl(item)
    // .unwrap_or_else(|err| err.to_compile_error())
    // .into()
}