Component children about sycamore HOT 5 CLOSED

New plan:
I want to eventually get rid of the component attribute macro and make components just functions that return Template<G>. This would be more idiomatic in Rust as well as reducing the number of proc-macros.

To make it more ergonomic to pass parameters to components, the template! macro will be modified to allow the following new syntax:

template! {
    Component(prop_1=2) {
        prop2=3
    }
    // or
    Component(prop_1=2, prop2=3)

Both syntaxes will mean the same thing.

from sycamore.

Maybe a huge changes, I agree on making sycamore more into a Rust instead of React or Yew. Can we break the template children as individual macro with designed patterns (traits). So it will not increase the complexity of template macro.

from sycamore.

How would this work if I want to have a component that only accepts specific children components? Say I want to force this structure:

Tabs {
    Tab(title="Tab 1") {
        h1 { "hey" }
    }
    Tab(title="Tab 2") {
        img(src="...")
    }
}

Or would it be up to the caller to ensure that only Tab components are passed to Tabs?

I'd prefer if we had something like yew where children of a component are enumerated.

from sycamore.

Can an example of how to use children in components be added to the documentation? I have the following minimal example (CSS and other parts of the page have been removed):

use sycamore::prelude::*;

#[component]
pub fn Card<'a, G: Html>(cx: Scope<'a>) -> View<G> {
    view! { cx,
	    div() {}
    }
}

fn main() {
    sycamore::render(|cx| view! { cx,
        Card {
	    p { "Test"}
	}
    });
}

This code compiles and displays correctly when p {"Test"} is commented out. However, when I try to include a paragraph within my Card component, I get this error.

error[E0599]: no method named `children` found for struct `UnitBuilder` in the current scope
  --> src/main.rs:13:27
   |
13 |       sycamore::render(|cx| view! { cx,
   |  ___________________________^
14 | |         Card {
15 | |         p { "Test"}
16 | |     }
17 | |     });
   | |_____^ method not found in `UnitBuilder`
   |
   = note: this error originates in the macro `view` (in Nightly builds, run with -Z macro-backtrace for more info)

I've tried changing the Card function to accept Props, but if that's the solution, I'm not able to figure out how to implement it correctly.

from sycamore.

@adamthrash yeah sorry the docs for 0.8 has some missing parts. I'll try to get to it soon.

from sycamore.