Fix recursion-limit build failure in the new item-card renderer
Deploy / deploy (push) Successful in 33s
Deploy / deploy (push) Successful in 33s
Same class of bug as the earlier ResourceValue/AnswerRow one: impl IntoView doesn't erase a component's concrete type within the same crate, so nested <For> children closures need their own explicit .into_any() at the call site, not just at the outer return - missing it on the two new <For>s (item list, item-card-fields) overflowed the query depth limit on release build. Verified locally with a full `cargo build --release` this time, not just cargo check. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
bd702bfbae
commit
43fa496778
+2
-1
@@ -851,7 +851,7 @@ fn ResourceValue(
|
||||
<For
|
||||
each=move || items.clone()
|
||||
key=|item| item.to_string()
|
||||
children=|item: serde_json::Value| view! { <ItemCard item=item/> }
|
||||
children=|item: serde_json::Value| view! { <ItemCard item=item/> }.into_any()
|
||||
/>
|
||||
</div>
|
||||
}
|
||||
@@ -928,6 +928,7 @@ fn ItemCard(item: serde_json::Value) -> impl IntoView {
|
||||
{v}
|
||||
</span>
|
||||
}
|
||||
.into_any()
|
||||
}
|
||||
/>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user