chore(deps): update leptos monorepo to v0.8.0-rc2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
leptos	workspace.dependencies	patch	0.8.0-rc1 -> 0.8.0-rc2
leptos_actix	workspace.dependencies	patch	0.8.0-rc1 -> 0.8.0-rc2
leptos_axum	workspace.dependencies	patch	0.8.0-rc1 -> 0.8.0-rc2
leptos_meta	workspace.dependencies	patch	0.8.0-rc1 -> 0.8.0-rc2
leptos_router	workspace.dependencies	patch	0.8.0-rc1 -> 0.8.0-rc2

---

Release Notes

leptos-rs/leptos (leptos)

v0.8.0-rc2

Compare Source

Release notes copied from 0.8.0-alpha/beta/rc1. Changelog relative to 0.8.0-rc1. This release includes some bugfixes, but is mostly intended to fix compilation on the latest nightly release.

0.8 has been planned for a while, primarily to accommodate small changes that arose during the course of testing and adopting 0.7, most of which are technically semver-breaking but should not meaningfully affect user code.

If we don't hear any feedback about issues with this rc2 release, we will plan to release it as 0.8.0 in the next week or so.

Noteworthy features:

• Axum 0.8 support. (This alone required a major version bump, as we reexport some Axum types.) (thanks to @​sabify for the migration work here)
• Significant improvements to compile times when using --cfg=erase_components, which is useful as a dev-mode optimization (thanks to @​zakstucke) This is the default setting for debug mode in future releases of cargo-leptos, and can be set up manually for use with Trunk. (See docs here.)
• Support for the new islands-router features that allow a client-side routing experience while using islands (see the islands_router example) (this one was me)
• Improved server function error handling by allowing you to use any type that implements FromServerFnError rather than being constrained to use ServerFnError (see #​3274). (Note: This will require changes if you're using a custom error type, but should be a better experience.) (thanks to @​ryo33)
• Support for creating WebSockets via server fns (thanks to @​ealmloff)
• Changes to make custom errors significantly more ergonomic when using server functions

As you can see this was a real team effort and, as always, I'm grateful for the contributions of everyone named above, and all those who made commits below.

WebSocket Example

The WebSocket support is particularly exciting, as it allows you to call server functions using the default Rust Stream trait from the futures crate, and have those streams send messages over websockets without you needing to know anything about that process. The API landed in a place that feels like a great extension of the "server function" abstraction in which you can make HTTP requests as if they were ordinary async calls. The websocket stuff doesn't integrate directly with Resources/SSR (which make more sense for one-shot things) but is really easy to use:

use server_fn::{codec::JsonEncoding, BoxedStream, ServerFnError, Websocket};

// The websocket protocol can be used on any server function that accepts and returns a [`BoxedStream`]
// with items that can be encoded by the input and output encoding generics.
//
// In this case, the input and output encodings are [`Json`] and [`Json`], respectively which requires
// the items to implement [`Serialize`] and [`Deserialize`].

#[server(protocol = Websocket<JsonEncoding, JsonEncoding>)]
async fn echo_websocket(
    input: BoxedStream<String, ServerFnError>,
) -> Result<BoxedStream<String, ServerFnError>, ServerFnError> {
    use futures::channel::mpsc;
    use futures::{SinkExt, StreamExt};
    let mut input = input; // FIXME :-) server fn fields should pass mut through to destructure

    // create a channel of outgoing websocket messages 
    // we'll return rx, so sending a message to tx will send a message to the client via the websocket
    let (mut tx, rx) = mpsc::channel(1);

    // spawn a task to listen to the input stream of messages coming in over the websocket 
    tokio::spawn(async move {
        while let Some(msg) = input.next().await {
            // do some work on each message, and then send our responses 
            tx.send(msg.map(|msg| msg.to_ascii_uppercase())).await;
        }
    });

    Ok(rx.into())
}

#[component]
pub fn App() -> impl IntoView {
    use futures::channel::mpsc;
    use futures::StreamExt;
    let (mut tx, rx) = mpsc::channel(1);
    let latest = RwSignal::new(None);

    // we'll only listen for websocket messages on the client
    if cfg!(feature = "hydrate") {
        spawn_local(async move {
            match echo_websocket(rx.into()).await {
                Ok(mut messages) => {
                    while let Some(msg) = messages.next().await {
                        latest.set(Some(msg));
                    }
                }
                Err(e) => leptos::logging::warn!("{e}"),
            }
        });
    }

    view! {
        <input type="text" on:input:target=move |ev| {
            tx.try_send(Ok(ev.target().value()));
        }/>
        <p>{latest}</p>
    }
}

What's Changed

• fix: call additional_context after providing other server context in all cases by @​gbj in https://github.com/leptos-rs/leptos/pull/3841
• fix: correctly decode base64-encoded server action error messages stored in URL by @​gbj in https://github.com/leptos-rs/leptos/pull/3842
• fix: don't try to move keyed elements within the DOM if they're not yet mounted (closes #​3844) by @​gbj in https://github.com/leptos-rs/leptos/pull/3846
• chore(nightly): update proc-macro span file name method name by @​gbj in https://github.com/leptos-rs/leptos/pull/3852
• fix: reactive_graph keymap impl and clippy warnings by @​sabify in https://github.com/leptos-rs/leptos/pull/3843
• chore: ran cargo outdated. by @​martinfrances107 in https://github.com/leptos-rs/leptos/pull/3722

Full Changelog: leptos-rs/leptos@v0.8.0-rc1...v0.8.0-rc2

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.