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

+6 -6
View File
@@ -36,22 +36,22 @@ fn blah() {
let handler = dioxus_liveview::new_handler()
.from_directory("abc123") // serve a given directory as the root
.with_context(|| SomeContext {}) // build out a new context for all of the server-rendered components to share
.with_route(SERVER_RENDERED_KEY, |ctx, props: &ServerRendered| {
.with_route(SERVER_RENDERED_KEY, |ctx: &ServerRendered| {
//
})
.with_route(SERVER_RENDERED_KEY, |ctx, props| {
.with_route(SERVER_RENDERED_KEY, |ctx| {
//
})
.with_route(SERVER_RENDERED_KEY, |ctx, props| {
.with_route(SERVER_RENDERED_KEY, |ctx| {
//
})
.with_route(SERVER_RENDERED_KEY, |ctx, props| {
.with_route(SERVER_RENDERED_KEY, |ctx| {
//
})
.with_route(SERVER_RENDERED_KEY, |ctx, props| {
.with_route(SERVER_RENDERED_KEY, |ctx| {
//
})
.with_route(SERVER_RENDERED_KEY, |ctx, props| {
.with_route(SERVER_RENDERED_KEY, |ctx| {
//
})
// depend on the framework, build a different type of handler