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
Currently, leptos uses a few bespoke Into traits. While they get the job done, using the traits from std::convert would be more idiomatic, and I suspect it would make Leptos play nicer with other dependencies developers may use.
I'll work on this one.
The text was updated successfully, but these errors were encountered:
For context: These separate traits come from the 0.4-and-earlier period when they required an additional Scope argument that is no longer used in 0.5, and they will likely not exist in the next meaningful version change. Feel free to experiment with something like implementing From<T> for Attribute where T: IntoAttribute or whatnot, but obviously removing the traits themselves would be a breaking change and replacing all the -> impl IntoView and so on with -> impl Into<View> is just churn. Having a separate IntoView trait in particular allows a lot of flexibility, as there is no View enum in the next version of the renderer.
@gbj I'll experiment with Into<Attribute>. I was banging my head against the wall trying to get Into<View> working, but will hold off on that since View is going away anyway.
Is there anywhere I can keep an eye on what's being done with the renderer you mentioned?
Currently, leptos uses a few bespoke Into traits. While they get the job done, using the traits from std::convert would be more idiomatic, and I suspect it would make Leptos play nicer with other dependencies developers may use.
I'll work on this one.
The text was updated successfully, but these errors were encountered: