Feat: massive changes to definition of components

This change switches back to the original `ctx<props>` syntax for
commponents. This lets lifetime elision to remove the need to match
exactly which lifetime (props or ctx) gets  carried to the output. As
such, `Props` is currently required to be static. It *is* possible to
loosen this restriction, and will be done in the future, though only
through adding metadata about the props through the Props derive
macro. Implementing the IS_STATIC trait is unsafe, so the derive macro
will do it through some heuristics.

For now, this unlocks sharing vnodes from parents to children, enabling
pass-thru components, fragments, portals, etc.
This commit is contained in:
Jonathan Kelley committed 2021-06-01 18:33:15 -04:00
1 parent c1fd848f89
commit 508c560320
82 files changed
+692 -558

No files matched your search

+4 -4
View File
@@ -1,4 +1,4 @@
//! Basic example that renders a simple domtree to the browser.
//! Basic example that renders a simple VNode to the browser.
use dioxus_core::prelude::*;
use dioxus_web::*;
@@ -12,7 +12,7 @@ fn main() {
wasm_bindgen_futures::spawn_local(WebsysRenderer::start(App));
}
static App: FC<()> = |ctx, _| {
static App: FC<()> = |ctx| {
ctx.render(rsx! {
div {
h1 {"hello"}
@@ -22,7 +22,7 @@ static App: FC<()> = |ctx, _| {
})
};
static C1: FC<()> = |ctx, props| {
static C1: FC<()> = |ctx| {
ctx.render(rsx! {
button {
"numba 1"
@@ -30,7 +30,7 @@ static C1: FC<()> = |ctx, props| {
})
};
static C2: FC<()> = |ctx, props| {
static C2: FC<()> = |ctx| {
ctx.render(rsx! {
button {
"numba 2"