Merge port of yew-autoprops in Yew to yew-autoprops

[cecton]

Fixes #8 Fixes #7 Fixes #9 Fixes #3 Related to https://github.com/yewstack/yew/pull/3505

[cecton]

cc @kirillsemyonkin

[kirillsemyonkin]

Seems like its generating an unexpected comma somewhere (be it struct or fn) when there are no props but there are generic types

[kirillsemyonkin]

Repro:

#[autoprops]
#[function_component]
pub fn Test<T>() -> Html {
    html! {}
}

[cecton]

@kirillsemyonkin fixed

[kirillsemyonkin]

I think to trigger CI you may wanted to rerun all jobs, sometimes I see that button in the actions section

[cecton]

No I really wanted to trigger the CI with a different commit hash ^_^

[cecton]

TIL that you need to add the rust version in swatinem/cache key for it to work properly :woman_facepalming: I have like 10 repos that are not doing that huh

[kirillsemyonkin]

Here is another one

[cecton]

Fixed

[kirillsemyonkin]

1. Autoprops does not require -> Html on the fn, nor HtmlResult works (seems like that is replaced by Html) - following does not work:

#[autoprops]
#[function_component]
pub fn Test() -> HtmlResult {
    Ok(html! {})
}

2. Defaults for fn generic type params are ignored by Rust, here are three cases (doesnt work, good; works, good; doesnt work, oops):

[cecton]

@kirillsemyonkin fixed

[cecton]

@hamza1311 @kirillsemyonkin ok I think this is ready now

[kirillsemyonkin]

What is the current status of this?

[cecton]

@yewstack/yew can I have a final review on this?

[Madoshakalaka]

@cecton hi you are my angel, thanks for the work

[kirillsemyonkin]

@yewstack/yew can I have a final review on this?

Can we skip such a review since it is more-or-less separate from Yew and proceed to merge? We can have extra merges later, independent of Yew's slow cycle

[kirillsemyonkin]

Ideally anyone's work on a stylist PR for #[styled_component] -> #[styled] (for #[styled] #[autoprops] #[component] progress) should happen somewhere around now as well

[cecton]

Can we skip such a review since it is more-or-less separate from Yew and proceed to merge? We can have extra merges later, independent of Yew's slow cycle

Yeah I think the other maintainers are a bit overbooked at the moment so let's merge it as is. Worst case scenario we open issues or fix things later on.