Plays badly with cfg attribute

[Madoshakalaka]

this works:

#[derive(PartialEq, Properties)]
pub struct FooProps {
    #[cfg(feature = "foo")]
    pub foo: bool,
}


#[function_component]
pub fn Foo(props: &FooProps) -> Html {
    html! {}
}

but this doesn't compile when the cfg is not satisfied:

#[autoprops]
#[function_component]
pub fn Foo(#[cfg(feature = "foo")] foo: bool) -> Html {
    html! {}
}

it fails with

struct `app::FooProps` does not have a field named `foo`

[kirillsemyonkin]

Honestly I do not remember what the stance on cfgs (or other attributes, for that matter) was. Try reading discussions, give some suggestions, maybe its obvious idk.

For the time being, try cfging the whole component with and without the necessary props:

#[cfg(feature = "foo")] 
#[autoprops]
#[function_component]
pub fn Foo(foo: bool) -> Html {
    html! {}
}

#[cfg(not(feature = "foo"))] 
#[autoprops]
#[function_component]
pub fn Foo() -> Html {
    html! {}
}

[Madoshakalaka]

I have a Button component with a dozen props, and I only want to feature gate a single data_cy attribute for e2e testing use.

I think it's a very legitimate use case as cypress recommends adding data-cy attributes and it doesn't make sense to include these attributes in production builds.

Creating two Button components while repeating most of the props and component body feels a bit too verbose

[kirillsemyonkin]

Creating two Button components while repeating most of the props and component body feels a bit too verbose

I know, which is why I mentioned it being a temporary solution ("For the time being")