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
I expected this to generate a <button> with a data-my-attr attribute, but in the actual HTML generated, the button does not have that attribute.
Use case: I want to use this to dynamically add some data- attributes. The exact attributes to set are defined by one of the props being passed in, but that Prop is a custom struct and the logic for which attributes to add to the button should live in that struct's module, not here.
Leptos Dependencies
Please copy and paste the Leptos dependencies and features from your Cargo.toml.
For example:
leptos = { version = "0.4", features = ["nightly"] }
leptos_axum = { version = "0.4", optional = true }
leptos_meta = { version = "0.4", features = ["nightly"] }
leptos_router = { version = "0.4", features = ["nightly"] }
The text was updated successfully, but these errors were encountered:
Oh interesting, I thought the view! macro was just expanding to code using the builder pattern since it does return a type usable in the builder pattern.
If they are really incompatible, I think this should at least throw a run time panic. Better a build time error. Being silent but doing the wrong thing isn't great.
Describe the bug
I expected this to generate a
<button>
with adata-my-attr
attribute, but in the actual HTML generated, the button does not have that attribute.Use case: I want to use this to dynamically add some
data-
attributes. The exact attributes to set are defined by one of the props being passed in, but that Prop is a custom struct and the logic for which attributes to add to the button should live in that struct's module, not here.Leptos Dependencies
Please copy and paste the Leptos dependencies and features from your
Cargo.toml
.For example:
The text was updated successfully, but these errors were encountered: