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

KeySpace KeyType is not handled #144

Closed
rosmanov opened this issue Apr 26, 2022 · 5 comments · Fixed by #161
Closed

KeySpace KeyType is not handled #144

rosmanov opened this issue Apr 26, 2022 · 5 comments · Fixed by #161
Assignees
Labels
bug Something isn't working

Comments

@rosmanov
Copy link

rosmanov commented Apr 26, 2022

bubbletea has recently changed the KeyType for the space character.

As a result, in particular, nothing happens when the user enters space in the textinput component.

We need to add a case tea.KeySpace: somewhere around these lines.


bubbles revision is 292a1dd7ba97b1dc96a12d5ba50301cc731ef37f (current master)

@meowgorithm
Copy link
Member

Hi! @bashbunni just fixed this in charmbracelet/bubbletea#289. It will be available in the next release of Bubble Tea. If you need the functionality immediately you can pin to master.

Sorry for the confusion!

@meowgorithm
Copy link
Member

meowgorithm commented Apr 26, 2022

Apologies, I completely misread this one. This is a very good catch. We'll correct this one shortly. Thank you for filing this.

@bashbunni
Copy link
Member

@meowgorithm let me know if this is still a wip but saw it was merged

@meowgorithm
Copy link
Member

meowgorithm commented May 23, 2022

Merged in master on the Bubble Tea side, so we do need to make this change after all. Let’s get this one in a PR and queue it up to be merged right after the next Bubble Tea release.

@meowgorithm
Copy link
Member

This is now fixed for both the present and the upcoming Bubble Tea versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants