Implement Navigation
bubble for routing
#701
Replies: 5 comments
-
I'd love to pick this up and contribute! How should I move forward? |
Beta Was this translation helpful? Give feedback.
-
Hey @KaviiSuri, awesome that you want to contribute. I think to implement this we'll need some sort of I think a lot of the inspiration will come from this video of making nested models (https://www.youtube.com/watch?v=uJ2egAkSkjg) and making a way to stream line this code and make concepts that most people would understand so that it is easier to build multi-view applications. If you want to give it a go please feel free to! Let me know if you have any further questions or want to ask about clarification about introducing concepts. |
Beta Was this translation helpful? Give feedback.
-
Hi, Thanks for the video! I'll go through it and get back with any questions I have! |
Beta Was this translation helpful? Give feedback.
-
@maaslalani I've added a draft PR, wanted to get your inputs on how to move forward. |
Beta Was this translation helpful? Give feedback.
-
Hey, this isn't something we're planning on implementing at the moment. In an effort to tidy up our backlog of issues, I'm going to convert this to a discussion so we can track interest in this idea for future consideration. As for the attached PR, if you would like to make that component available to others, feel free to review the comments over there. There are community-maintained bubbles that will be linked in the official project README as well. |
Beta Was this translation helpful? Give feedback.
-
Bubbles should probably help users build multi-view applications such as
glow
, etc... more easily. We can likely do this by implementing routing and navigation through a Bubble similar to how we help define keybindings withkey.Binding
.I'm roughly imagining something like this:
I'd imagine we can also then implement many helper methods and handle updating nested models for most use cases.
I think this will make multi-view Bubble Tea applications much easier to implement if we can simply define several
tea.Model
and definekey.Binding
s to switch between them and handle all routing and updates for the users building the apps. This could also allow us to buildStack
based navigation, etc...Beta Was this translation helpful? Give feedback.
All reactions