let_unit_value violation within html macro

[Starwort]

Problem
Functional (and possibly struct?) components with no props (such as the routes generated by create-yew-app) cause violations of clippy::let_unit_value at their use sites.

Steps To Reproduce
Steps to reproduce the behavior:

1. Write a functional component with no props

   /// About page
   #[function_component(About)]
   pub fn about() -> Html {
       html! {
           {"Todo"}
       }
   }

2. Use the component within an invocation of html!:

   /// Switch app routes
   pub fn switch(routes: &AppRoute) -> Html {
       match routes.clone() {
           AppRoute::Home => html! { <Home /> },
           AppRoute::About => html! { <About /> },
           AppRoute::PageNotFound => html! { "Page not found" },
       }
   }

3. Run clippy under pedantic settings (cargo clippy -W clippy::pedantic)
4. See error

Expected behavior
No lint warning

Environment:

• Yew version: 0.19.3
• Rust version: 1.66.0-nightly (01af5040f 2022-10-04)
• Target, if relevant: Not sure, but shouldn't be relevant
• Build tool, if relevant: parcel-plugin-wasm.rs (shouldn't be relevant)
• OS, if relevant: Linux (shouldn't be relevant)

Questionnaire

• I'm interested in fixing this myself but don't know where to start
• I would like to fix and I have a solution
• I don't have time to fix this right now, but maybe later

[WorldSEnder]

Functional components with no properties get () assigned implicitly as <_ as BaseComponent>::Properties, which I would think is the cause of having such a let binding when constructing them in e.g. html! { <About /> }. A shame that clippy sees through the type aliases :D Thanks for the report!