0.7 todos

[gbj]

I have merged the leptos_0.7 branch from #2607 because it is much easier just to juggle main + PRs than main, a branch, PRs to main, and PRs to the branch!

Good first issues/PRs super welcome to fill in missing things:

• Resource::map and Resource::and_then (use 0.6 as baseline, should be very similar)
• Add in missing deprecated functions for things like create_blocking_resource and so on (or at least help compile a list of renamed functions that we can add deprecations for)

Outstanding feature TODOs, in order of priority

• Equivalent to a user implementing IntoView on an arbitrary struct (IntoRender)
• hot reloading (and therefore view markers)
• Resource::refetch()
• static routes
• Resource::once (with a relatively more efficient implementation)
• Await component (use Resource::once above)
• AnimatedShow
• Router/Route base
• Nested router set_is_routing
• SsrMode::PartiallyBlocked
• 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?)
• Reactive channel implementation for single-use signals
• trailing slash modes
• fallible hydration => start from suspense boundary
• AnimatedRoutes/AnimatedOutlet

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.)
• reading through docs to make sure they're consistent now

When ready for release

• updating book
• updating sandboxes
• making sure all docsrs docs build and are complete
• migrating templates to use the new versions of the templates

[dmgolembiowski]

• 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?)

@gbj Regarding this I was wondering if a js-sys generated binding to either of WebAssembly.compileStreaming() or WebAssembly.instantiateStreaming() could provide the hydration opportunity for a thing that hasn't been loaded yet?

For context:

The WebAssembly.instantiateStreaming() static method compiles and instantiates a WebAssembly module directly from a streamed underlying source. This is the most efficient, optimized way to load Wasm code.

I have a suspicion its importObject argument could be the collection of imports for which there is a separate leptos_lazy_{$sha}.wasm file corresponding to the DOM's expectation - like a collection of small polyfill files.