Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.7 todos #2771

Open
19 of 28 tasks
gbj opened this issue Aug 5, 2024 · 0 comments
Open
19 of 28 tasks

0.7 todos #2771

gbj opened this issue Aug 5, 2024 · 0 comments
Milestone

Comments

@gbj
Copy link
Collaborator

gbj commented Aug 5, 2024

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)

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant