build(deps): bump the leptos group with 3 updates

[dependabot]

Bumps the leptos group with 3 updates: leptos, leptos-use and leptos_axum.

Updates leptos from 0.6.15 to 0.7.0

Release notes

Sourced from leptos's releases.

v0.7.0

At long last, as the culmination of more than a year of work, the 0.7 release has arrived!

0.7 is a nearly-complete rewrite of the internals of the framework, with the following goals:

• maintain backwards compatibility for as much user application code as possible
• improve the async story and fix Suspense edge cases and limitations
• reduce WASM binary size
• reduce HTML size
• faster HTML rendering
• allow signals to be sent across threads
• enhance the ergonomics of things like prop spreading and accessing the HTML shell of your application
• build the foundation for future work
  • reactive stores to make nested reactivity more pleasant
  • client-side routing with islands and state preservation
  • integrating with native UI toolkits to create desktop applications

Getting Started

0.7 works with the current cargo-leptos version. If you want to start exploring, there are starter templates for Axum and Actix. Each template is only three files. They show some of the boilerplate differences; for more details, see below.

Axum: cargo leptos new --git https://github.com/leptos-rs/start-axum (repo) Actix: cargo leptos new --git https://github.com/leptos-rs/start-actix (repo)

New Features

.await on resources and async in <Suspense/>

Currently, create_resource allows you to synchronously access the value of some async data as either None or Some(_). However, it requires that you always access it this way. This has some drawbacks:

• requires that you null-check every piece of data
• makes it difficult for one resource to wait for another resource to load

Now, you can .await a resource, and you can use async blocks within a <Suspense/> via the Suspend wrapper, which makes it easier to chain two resources:

let user = Resource::new(|| (), |_| user_id());
let posts = Resource::new(
    // resources still manually track dependencies (necessary for hydration)
    move || user.get(),
    move |_| async move {
        // but you can .await a resource inside another
        let user = user.await?;
        get_posts(user).await
    },
);
view! {
<Suspense>
// you can .await resources to avoid dealing with the None state
<p>"User ID: " {move || Suspend::new(async move {
match user.await {
// ...
</tr></table>

... (truncated)

Commits

• d665dd4 v0.7.0
• be740b3 feat: add NodeRef::on_load() and writeable NodeRef (#3305)
• d2803c9 chore: remove pre-release message from README (#3075)
• f292244 fix: sort tuple-syntax class and style in addition to colon-syntax (closes #3...
• 292772c fix: allow a deprecated wasm-bindgen struct
• 5947aa2 Release rc3
• 6098836 docs: improve line location of hydration error message when using view macro ...
• 2dfa61f docs: fix help message for island macro (#3287)
• 4f39b0b Version any_spawner alongside other crates, reexport CustomExecutor (#3284)
• 980595f chore(deps): bump proc-macro2 from 1.0.91 to 1.0.92 (#3276)
• Additional commits viewable in compare view

Updates leptos-use from 0.13.11 to 0.14.0

Release notes

Sourced from leptos-use's releases.

Version 0.14.0

Changes in this version:

[0.14.0]

Highlights since 0.13

• Updated to Leptos 0.7
• Refactored ElementMaybeSignal and ElementsMaybeSignal to have a simpler implementation. For the vast majority of cases this should continue to work as before.
• Almost everything returned from functions is now Send + Sync.

Changes since 0.14.0-rc5

• Updated Leptos to use stable 0.7 version
• Updated wasm-bindgen to 0.2.96
• Updated web-sys 0.3.73

Special thanks to our sponsor:

• @​spencewenski

Version 0.14.0-rc5

Changes in this version:

[0.14.0-rc5] - 2024-11-27

• fixed error messages for get_header
• added Send + Sync to storage return closure

Special thanks to our sponsor:

• @​spencewenski

Version 0.14.0-rc4

Changes in this version:

[0.14.0-rc4] - 2024-11-26

• Updated to Leptos 0.7.0-rc2
• Fixed WASM on the serverside (thanks to @​GuillaumeDelorme)
• Fixed use_storage.
• Made all returned closures Send + Sync.

Special thanks to our sponsor:

• @​spencewenski

... (truncated)

Changelog

Sourced from leptos-use's changelog.

[0.14.0]

Highlights since 0.13

• Updated to Leptos 0.7
• Refactored ElementMaybeSignal and ElementsMaybeSignal to have a simpler implementation. For the vast majority of cases this should continue to work as before.
• Almost everything returned from functions is now Send + Sync.

Changes since 0.14.0-rc5

• Updated Leptos to use stable 0.7 version
• Updated wasm-bindgen to 0.2.96
• Updated web-sys 0.3.73

Special thanks to our sponsor:

• @​spencewenski

[0.14.0-rc5] - 2024-11-27

• fixed error messages for get_header
• added Send + Sync to storage return closure

Special thanks to our sponsor:

• @​spencewenski

[0.14.0-rc4] - 2024-11-26

• Updated to Leptos 0.7.0-rc2
• Fixed WASM on the serverside (thanks to @​GuillaumeDelorme)
• Fixed use_storage.
• Made all returned closures Send + Sync.

Special thanks to our sponsor:

• @​spencewenski

[0.14.0-rc3] - 2024-11-14

• Fixed potential SSR panic in use_locale(s) (thanks to @​veigaribo)
• Make use_locale prioritize user preferred locales over app preferred ones

[0.14.0-rc2] - 2024-11-10

• Updated to Leptos 0.7.0-rc1
• Updated to web-sys 0.3.72 and unpinned version (thanks to @​sabify)
• Added dependabot (thanks to @​sabify)
• Reverted use_user_media to have video enabled by default
• Fixed exponential increase on websocket reconnects

[0.14.0-rc1] - 2024-11-06

... (truncated)

Commits

• 1457623 Updated Cargo.toml
• 9e99f35 Updated CHANGELOG.md
• dc40a1c Merge pull request #205 from SleeplessOne1917/leptos-0.7-stable
• b8476c2 Update to stable Leptos 0.7
• 18cdd81 release 0.14.0-rc5
• d05ea79 fixed error messages for get_header
• 819b1bf added Send + Sync to storage return closure
• 123deb7 chore: rustfmt
• 74cf649 updated changelog
• 64bd75d chore: tests and warnings
• Additional commits viewable in compare view

Updates leptos_axum from 0.6.15 to 0.7.0

Release notes

Sourced from leptos_axum's releases.

v0.7.0

At long last, as the culmination of more than a year of work, the 0.7 release has arrived!

0.7 is a nearly-complete rewrite of the internals of the framework, with the following goals:

• maintain backwards compatibility for as much user application code as possible
• improve the async story and fix Suspense edge cases and limitations
• reduce WASM binary size
• reduce HTML size
• faster HTML rendering
• allow signals to be sent across threads
• enhance the ergonomics of things like prop spreading and accessing the HTML shell of your application
• build the foundation for future work
  • reactive stores to make nested reactivity more pleasant
  • client-side routing with islands and state preservation
  • integrating with native UI toolkits to create desktop applications

Getting Started

0.7 works with the current cargo-leptos version. If you want to start exploring, there are starter templates for Axum and Actix. Each template is only three files. They show some of the boilerplate differences; for more details, see below.

Axum: cargo leptos new --git https://github.com/leptos-rs/start-axum (repo) Actix: cargo leptos new --git https://github.com/leptos-rs/start-actix (repo)

New Features

.await on resources and async in <Suspense/>

Currently, create_resource allows you to synchronously access the value of some async data as either None or Some(_). However, it requires that you always access it this way. This has some drawbacks:

• requires that you null-check every piece of data
• makes it difficult for one resource to wait for another resource to load

Now, you can .await a resource, and you can use async blocks within a <Suspense/> via the Suspend wrapper, which makes it easier to chain two resources:

let user = Resource::new(|| (), |_| user_id());
let posts = Resource::new(
    // resources still manually track dependencies (necessary for hydration)
    move || user.get(),
    move |_| async move {
        // but you can .await a resource inside another
        let user = user.await?;
        get_posts(user).await
    },
);
view! {
<Suspense>
// you can .await resources to avoid dealing with the None state
<p>"User ID: " {move || Suspend::new(async move {
match user.await {
// ...
</tr></table>

... (truncated)

Commits

• d665dd4 v0.7.0
• be740b3 feat: add NodeRef::on_load() and writeable NodeRef (#3305)
• d2803c9 chore: remove pre-release message from README (#3075)
• f292244 fix: sort tuple-syntax class and style in addition to colon-syntax (closes #3...
• 292772c fix: allow a deprecated wasm-bindgen struct
• 5947aa2 Release rc3
• 6098836 docs: improve line location of hydration error message when using view macro ...
• 2dfa61f docs: fix help message for island macro (#3287)
• 4f39b0b Version any_spawner alongside other crates, reexport CustomExecutor (#3284)
• 980595f chore(deps): bump proc-macro2 from 1.0.91 to 1.0.92 (#3276)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml