(draft) Leptos 0.7

[gbj]

(Opening this so that I can start tracking test/docs/example coverage)

Things I'd like to achieve before a beta release

• Clear all warnings (todo!() is okay)
• Complete docs
• All tests passing in core
• Actix integration
• All examples either a) ported, b) missing features listed in TODOs, or c) moved to projects

Incomplete list of feature TODOs

• nonces
• .await on resources: clone by default for IntoFuture, with alternate method to read them by reference
• Setting ResponseOptions in integrations
• local resources (resources that only run on the client, not server)
• <ProtectedRoute/>
• Render individual Suspend(_) without a <Suspense/>
• Nested router set_is_routing
• Attribute spreading for attributes on <Body/> etc. instead of Vec<AnyAttribute>
• Directives
• Equivalent to a user implementing IntoView on an arbitrary struct
• Figuring out the interaction between Lazy routes and hydration (what do you do while hydrating if the code for the route hasn't been lazy-loaded yet?)
• path!() macro to make route definitions easier in router
• Reactive channel implementation for single-use signals
• blocking resources
• partially-blocked SSR
• Thread-local arena that yields Copy but !Send for !Send data (like browser things)
• global class support
• hot reloading (and therefore view markers)
• static routes
• trailing slash modes
• Router/Route base
• custom elements/custom attributes
• fallible hydration => start from suspense boundary
• add GlobalAttributes methods for on____ HTML attributes

Forward-ported bug fixes (things that have been fixed on 0.6 but reimplemented in 0.7, and need to be checked)

• pending action dispatches (Fix of #2652 #2653)
• unescaping during navigation (fix: do not unescape / and other route characters when following a link #2651)
• ownership and disposal fixes and tests (fix: ensure everything is disposed of consistently #2639)
• ToChildren docs (docs: Add docs for ToChildren #2643)
• fix: try_with should not panic on disposed resources (closes #2620) #2621

Finalizing:

• simplify tachys APIs by removing duplicated content (HTML length, checking on template duplication, etc.)

[NiklasEi]

Will there be follow-up tickets for tracking the open tasks from this PR? I am mainly interested in static routes, but some of the other open points certainly are big enough to also be tracked on their own.

[gbj]

@NiklasEi Yes, it is just way easier to manage a single main branch once people start making PRs, and it was time! Everything else will be completed. I will probably just create a single tracking item that copy-pastes the list above.