What is Leptos Roadmap for now? #3616
Replies: 3 comments 2 replies
-
There is an open PR for the next release. More broadly, if you look back at the pinned "Roadmap 2023-24" issue, you'll see there are a few "open checkmarks" there improving the client-side routing story for islands. This needed to be built on the back of the work that built toward 0.7, but now exists here and will be incorporated in 0.8 most likely. Building code-splitting/lazy-loading into The framework is more or less feature complete, otherwise. So you can probably expect the code splitting work to land, some incremental improvements in build tooling, and no particularly meaningful breaking changes in the future. |
Beta Was this translation helpful? Give feedback.
-
Faster dev builds are imminent with 0.8 but what do you mean "better editor experience"?
…On Sat, Feb 15, 2025, at 8:05 AM, Matin Mohammadi wrote:
Thanks for your time and effort! I'd love to see a better editor experience and faster builds, and hopefully, we will see Leptos as a serious alternative to JS-based frameworks.
—
Reply to this email directly, view it on GitHub <#3616 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVBTCPMY6JN5MJ4IO2CFZD2P5QS5AVCNFSM6AAAAABXGSWCKOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGA2DMOI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
The good news for you here is that if you use Neovim, we have a treesitter plugin that does exactly this. It should be relatively easy for a Zed or Helix user to add it as a plugin, but so far no one has done so. I talk about my IDE setup here:
https://benw.is/posts/easy-leptos-editor
Everything else is up to the developers of the IDE or require a different highlighting setup(VsCode, emacs). I don't think developing those is something on our roadmap.
…On Sat, Feb 15, 2025, at 11:49 AM, Matin Mohammadi wrote:
I think the `view!` macro can have proper syntax highlighting and autocomplete for both HTML and the Rust code and also autocomplete for libs like HTMX, Tailwind, etc. can be nice.
Although I understand that these will likely need some kind of LSP to be made, I think it is worth the DX boost.
—
Reply to this email directly, view it on GitHub <#3616 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVBTCLAJEKWX7KPAASRYND2P6K6BAVCNFSM6AAAAABXGSWCKOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGE3DCOI>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What is currently planned for the next release of Leptos?
Beta Was this translation helpful? Give feedback.
All reactions