Who’s ready for Bubble Tea v2 Alpha?

[bashbunni]

Hey everyone, we’re officially launching the Bubble Tea v2 alpha.

If you’re curious to know what the changes are and how to get started using it, check out the release notes. The examples on that branch are also up-to-date with the new v2 API changes, so you can totally use those to guide you.



What we would love from you is to have you try it and give us feedback. The best place to put your thoughts is here, in the announcement on GitHub. You can totally chat on Discord about it too, but the team can only really keep track of what’s on GitHub. 

If you run into any issues, please file an issue on the Bubble Tea repo with (v2) in the title.







We’re super excited to share this with you all!

[dogwaterdev1]

YOOO LETS GOOOOO

[NachoNievaG]

Oh, this is going to be a wild ride 🚀

[blacktop]

I know there was a separate repo that added mouse support, but does v2 add native mouse support to bubbletea?

[bashbunni]

Hey @blacktop yes, Bubble Tea should have full mouse support in v2 alpha. This is from the release notes

We've also improved the mouse API, which is a breaking change. Use
tea.MouseMsg to match against different types of mouse events. Mouse messages
are split into tea.MouseClickMsg, tea.MouseReleaseMsg, tea.MouseWheelMsg,
and tea.MouseMotionMsg.

@aymanbagabas let me know if I'm missing any details here :)

[aymanbagabas]

Bubble Tea v1 and v2 both support mouse events.

[sa-]

Honestly that's fire

[ignoxx]

great changes 🚀

[Broderick-Westrope]

Awesome to see this progress. Unfortunately I haven't been able to get the KeyRelease to work in this minimal example. I'm using WezTerm version "20240203-110809-5046fc22" on MacOS.

Would appreciate any help :)

[meowgorithm]

Hey! I think this is a known, and somewhat contested, issue in Alacritty (but @aymanbagabas correct me if I’m wrong)

alacritty/alacritty#7435

[Broderick-Westrope]

Im using WezTerm. Are you suggesting it may also be an issue in WezTerm?

[bashbunni]

Hey, just to confirm, do you have enable_kitty_keyboard=true in your wezterm config? I'm just looking through the issues in the wezterm repo related to kitty keyboard https://github.com/search?q=repo%3Awez%2Fwezterm+kitty+keyboard&type=issues

[meowgorithm]

Apologies, @Broderick-Westrope I totally misread. I can confirm that config.enable_kitty_keyboard = true solves this in Wezterm (thanks @bashbunni).

[aymanbagabas]

I can confirm enabling kitty keyboard in the config solves the issue. Also related #1161

[AdditionAddict]

new to charm (and go) but new api changes make so much more sense esp. key messages, got very confused by v1 how to do switch statements. love the changes!

[GeertJohan]

Very nice improvements!

Is there space to adress #434 in v2?
A major version is a good moment to do this because it probably needs a breaking change.

[meowgorithm]

Your point are very apt, though I will say we're hesitant to stray too far from Bubble Tea's functional roots, understanding completely the concern that Bubble Tea isn't idiomatic Go in places and also that Go is a decidedly imperative language.

A few questions:

1. Would this change require models to be pointers themselves? In other words, always &model{} and never model{}.
2. There are some very effective techniques that can come from being able to switch models entirely when returning, which I don't think is possible without being able to return a model. Am I correct here? For example:

func (m Model) Update(msg tea.Msg) (tea.Model, tea.Cmd) {
    if someCondition {
        return someOtherModel{}.Init()
    }
    return m, nil
}

[GeertJohan]

Hey @meowgorithm!

1. Implementations of Model can be stored as values (var m = myModel{}), but when they are passed to functions that expect the Model interface they must be passed as a pointer. This is no different from the current situation and is a result of how interfaces work. Example: https://go.dev/play/p/bK0FwkIYudk

2. That won't be possible. It's ofcourse nice that this is currently possible with a small amount of code, but it also feels like it is unexpected of a model to do that. I would personally prefer to be more explicit about such a thing; using a wrapping model that switches from the first to the second model. There could be communication from the first model to the wrapper which causes the wrapper to swap it out for the second model. This will be more code, but also more explicit. And thereby easier to read, understand and maintain.

[qualidafial]

@GeertJohan 1. Your example only needs to use a pointer because your FooModel.Update method is implemented with a (f *FooModel) receiver. If I change the receiver to (f FooModel) then I can call runUpdate(fooModelValue) without taking fooModelValue's address. https://go.dev/play/p/X4_prtoj9Z4.

With that said, there is nothing stopping you from using pointer receivers for your tea.Model implementations today, as long as your Init, Update, and View all use the same receiver type, and you pass the struct pointer to tea.NewProgram().

[GeertJohan]

Hi @qualidafial I understand that the receiver beeds to be a pointer, but I don't think that's what @meowgorithm was referring to.

Also understand the pointer receiver is currently possible, this is more about removing ambiguity and increasing consistency. See #434

[qualidafial]

Understood. I do think that the similarity of tea.Model to bubbles component APIs like list.Model or textinput.Model, coupled with the fact they don't actually implement tea.Model was very confusing when I was getting started with bubbletea.

Possibly we could preserve the ability to switch to a new model via a special tea.Cmd e.g. tea.SetModel(newModel)

[qualidafial]

What is the team's v2 release plan wrt bubbles, lipgloss, and so on? Are there active v2 branches being worked on, or are we trying to nail down bubbletea first?

[meowgorithm]

We're planning on releasing v2s of Bubble Tea, Bubbles, Lip Gloss, and Huh all around the same time. All branches are in active development and we'll most likely see a v2 alpha for Lip Gloss next.

[eduardoagarcia]

I'm excited for this! What's the ETA for this release?

[aymanbagabas]

Hey @eduardoagarcia! No ETA yet, but you can use the alpha version and tell us if you find any bugs or concerns

go get github.com/charmbracelet/bubbletea/v2@v2.0.0-alpha.1

[bashbunni]

Update on this, v2-alpha.2 is live! #1237