Need help with a proc macro meant to run inside of rsx!

[Nejat]

hi, i need help with a macro i am working on, that is meant to be called from with in rsx!()

i've been working on a proc macro crate to easily derive standard html dom attributes and events for custom components

the idea is to extend a Props struct easily, for example

use dioxus::prelude::*;

use dioxus_sugar::{apply_attributes, attributes};

#[attributes(optional(div), exclude(class, name, id))]
#[events(keyboard, exclude(onkeypress))]
#[classes(color)]
#[derive(Props)]
struct Props<'a> {
    #[props(default)]
    class: &'a str,
    color: Color,
    children: Element<'a>,
}

fn component<'a>(cx: Scope<'a, Props<'a>>) -> Element {
    cx.render(rsx! {
        div {
            apply_attributes!{ cx; div, exclude(class, name, id) }
            &cx.props.children
        }
    })
}

There are three custom attributes and eventually two or three proc macros.

Attributes

#[attributes] - which extends the struct definition with attributes,

you can include:

• individual attributes, i.e. href, id, class, etc.
• tags, which will include all the attributes of the tag, i.e. div
• all tags in a specific category; basic, formatting, forms, frames, images, etc.,
• global attributes

you can use an optional list to make the fields optional and decorated with a #[props(optional)] attribute

you can use a default list to use defaults or assign specific defaults, i.e. #[attributes(default(disabled = true))]

you can use an exclude list to skip individual attributes from the list

Events

#[events] - which extends the struct definition with events

you can include:

• individual events, i.e. onclick, onkeypress , etc.
• all events of a category, keyboard, mouse, etc.

you can use an exclude list to remove individual attributes from the list

* as i write this, i realize i could add support for all events of a tag too

Classes

#[classes] - marks fields on the struct to be included in the implemented Display trait of the struct intended to be rendered in the class attribute in the component.

* I'm not convinced this implementation is clear/logical and will consider a better alternative if anyone has a suggestion.

Based on Standards

i created another crate to parse the html standard to ensure that only html 5 attributes and events can be specified

Apply Attributes

apply_attributes! - is intended to tie it all to getter and apply fields to an internal html tag of your choosing, even spreading the values are to multiple tags.

and this is where i need help ...

parsing seems to be working

i'm having issues tokenizing, for the example above i get the following compile error

error: expected type, found `"{ cx.props.accesskey }"`
  --> tests\apply_attributes_tests.rs:16:13
   |
16 |             apply_attributes!{ cx; div, exclude(class, name, id) }
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |             |
   |             expected type
   |             tried to parse a type due to this
   |
   = note: this error originates in the macro `apply_attributes` (in Nightly builds, run with -Z macro-backtrace for more info)

i am tokenizing the individual fields as if i'm writing them by hand and i guess the order of how rsx! runs nested macros might affect this, but i am not really sure where to go from here.

your help with this would be amazing, thanks

the repo is here dioxus-sugar

The master branches works for all three attribute macros described above, the code in question is in the branch feature\apply_attributes_macro

[Nejat]

The following is a debug dump of the token stream of the applied macro, which works when copied to the example code.

accesskey : "{cx.props.accesskey:?}", contenteditable :
"{cx.props.contenteditable:?}", dir : "{cx.props.dir:?}", draggable :
"{cx.props.draggable:?}", hidden : "{cx.props.hidden:?}", lang :
"{cx.props.lang:?}", spellcheck : "{cx.props.spellcheck:?}", style :
"{cx.props.style:?}", tabindex : "{cx.props.tabindex:?}", title :
"{cx.props.title:?}", translate : "{cx.props.translate:?}",

I've added it as second component in the test and pushed it to the repo for reference