You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It seems like SignalSetter wrapper type should be in the prelude just like the Signal wrapper type is.
The query_signal() signal generator requires it therefore, I generally take #[prop(into)] set_foo: SignalSetter<T>, in my components when I need a writer so am annoyed when I have to add the specific import below my use leptos::prelude::*;
Describe the solution you'd like
I'd like SignalSetter added to the prelude.
Describe alternatives you've considered
It seems that (from a quick search) query_signal() is the only signal generator that produces a SignalSetter, so it may be reasonable to leave SignalSetter out of the prelude as an uncommon type.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It seems like
SignalSetter
wrapper type should be in the prelude just like theSignal
wrapper type is.The
query_signal()
signal generator requires it therefore, I generally take#[prop(into)] set_foo: SignalSetter<T>,
in my components when I need a writer so am annoyed when I have to add the specific import below myuse leptos::prelude::*;
Describe the solution you'd like
I'd like
SignalSetter
added to the prelude.Describe alternatives you've considered
It seems that (from a quick search)
query_signal()
is the only signal generator that produces aSignalSetter
, so it may be reasonable to leaveSignalSetter
out of the prelude as an uncommon type.The text was updated successfully, but these errors were encountered: