docs: format

This commit is contained in:
Greg Johnston 2023-09-08 16:27:50 -04:00
parent a07984be9e
commit 2fa2bf1706
2 changed files with 11 additions and 10 deletions

View file

@ -769,11 +769,12 @@ impl<El: ElementDescriptor + 'static> HtmlElement<El> {
if matches!(self.children, ElementChildren::Chunks(_)) {
let location = std::panic::Location::caller();
crate::warn!(
"\n\nWARNING: At {location}, you call .dyn_classes() on an \
HtmlElement<_> that was created with the `view!` macro. \
The macro applies optimizations during SSR that prevent \
calling this method successfully. You should not mix the \
`view` macro and the builder syntax when using SSR.\n\n",
"\n\nWARNING: At {location}, you call .dyn_classes() on \
an HtmlElement<_> that was created with the `view!` \
macro. The macro applies optimizations during SSR that \
prevent calling this method successfully. You should not \
mix the `view` macro and the builder syntax when using \
SSR.\n\n",
);
}
}
@ -1103,10 +1104,10 @@ impl<El: ElementDescriptor + 'static> HtmlElement<El> {
{
let location = std::panic::Location::caller();
crate::debug_warn!(
"\n\nWARNING: At {location}, you call .child() on an \
HtmlElement<_> that was created with the `view!` \
macro. The macro applies optimizations during \
SSR that prevent calling this method \
"\n\nWARNING: At {location}, you call .child() on \
an HtmlElement<_> that was created with the \
`view!` macro. The macro applies optimizations \
during SSR that prevent calling this method \
successfully. You should not mix the `view` \
macro and the builder syntax when using SSR.\n\n"
);

View file

@ -808,7 +808,7 @@ pub fn slot(args: proc_macro::TokenStream, s: TokenStream) -> TokenStream {
/// form data using [`serde_qs`](https://docs.rs/serde_qs/latest/serde_qs/) or as `application/cbor`
/// using [`cbor`](https://docs.rs/cbor/latest/cbor/). **Note**: You should explicitly include `serde` with the
/// `derive` feature enabled in your `Cargo.toml`. You can do this by running `cargo add serde --features=derive`.
/// - **Context comes from the server.** Server functions are provided access to the HTTP request and other relevant
/// - **Context comes from the server.** Server functions are provided access to the HTTP request and other relevant
/// server data via the server integrations, but they do *not* have access to reactive state that exists in the client.
/// - Your server must be ready to handle the server functions at the API prefix you list. The easiest way to do this
/// is to use the `handle_server_fns` function from [`leptos_actix`](https://docs.rs/leptos_actix/latest/leptos_actix/fn.handle_server_fns.html)