Document 0.7-rc.1 breaking changes

[ealmloff]

A bunch more breaking changes were added in the 0.7-rc.1 release. We should document them in the migration guide:

• The server context is gone
• Server functions return a different error type
• Server function data encodings are gone
• Middleware support is gone
• Multiple error support for the error boundary was removed
• The dioxus error type is no longer clone which means you can't call most resources like functions
• RSX context methods thrown from children to boundaries for errors and suspense are gone
• index.html support is gone

These changes also break a significant chunk of the doc examples that are checked (and likely more that are unchecked). We should go through each example and check them again before the release or address #537

[jkelleyrtp]

Server functions return a different error type

You can still use ServerFnError but you can also use anyhow::Error, StatusCode, and HttpError.

RSX context methods thrown from children to boundaries for errors and suspense are gone

throw_error still exists as a free function - are you referring to methods on ScopeId?

The dioxus error type is no longer clone which means you can't call most resources like functions

The change here was moving to anyhow::Error and then exposing CapturedError as the more flexible, cloneable, error type. Maybe we can change dioxus::Ok to return Result<T, CapturedError>? CapturedError implements From<T> where T: Into<anyhow::Error> so it should work the same as before.

Middleware support is gone
The server context is gone

I never got around to plugging back per-request middleware - since you can apply per-request guards and per-router layers, you might not need it anymore?

[ealmloff]

RSX context methods thrown from children to boundaries for errors and suspense are gone

throw_error still exists as a free function - are you referring to methods on ScopeId?

These two methods to add rsx to errors and suspense were removed:

• https://docs.rs/dioxus/0.6.3/dioxus/prelude/trait.SuspenseExtension.html#tymethod.with_loading_placeholder
• https://docs.rs/dioxus/0.6.3/dioxus/prelude/trait.Context.html#tymethod.show

The change here was moving to anyhow::Error and then exposing CapturedError as the more flexible, cloneable, error type. Maybe we can change dioxus::Ok to return Result<T, CapturedError>? CapturedError implements From<T> where T: Into<anyhow::Error> so it should work the same as before.

The dioxus::Result type we returned from some resources in examples isn't clone which breaks code like this:

use dioxus::prelude::*;

fn main() {}

fn fetch_dog_image(breed: impl Display) -> impl Future<Output = dioxus::Result<String>> {
    async move {
        let response = reqwest::get(format!("https://dog.ceo/api/breed/{breed}/images/random"))
            .await?
            .json::<DogApi>()
            .await?;
        dioxus::Ok(response.message)
    }
}

#[component]
fn DogView() -> Element {
    let poodle_img = use_resource(|| fetch_dog_image("poodle"));

    let poodle_img = match poodle_img() {
        Some(Ok(src)) => src,
        _ => {
            return rsx! {
                p { "Loading or error..." }
            };
        }
    };

    let golden_retriever_img = use_resource(|| fetch_dog_image("golden retriever"));

    let golden_retriever_img = match golden_retriever_img() {
        Some(Ok(src)) => src,
        _ => {
            return rsx! {
                p { "Loading or error..." }
            };
        }
    };

    let pug_img = use_resource(|| fetch_dog_image("pug"));

    let pug_img = match pug_img() {
        Some(Ok(src)) => src,
        _ => {
            return rsx! {
                p { "Loading or error..." }
            };
        }
    };

    rsx! {
        div {
            h1 { "Dog Images" }
            img { src: "{poodle_img}" }
            img { src: "{golden_retriever_img}" }
            img { src: "{pug_img}" }
        }
    }
}

I never got around to plugging back per-request middleware - since you can apply per-request guards and per-router layers, you might not need it anymore?

Not all of these are regressions, but we should document how to do middleware/layers to specific server functions in the migration guide