Tapioca #7
Replies: 1 comment 9 replies
-
|
Hey there! I personally think this would make a great addition. Are you open to changing the name? Glitter has some history at Charm and we've set the name aside for a possible future project. |
Beta Was this translation helpful? Give feedback.
-
|
@bashbunni has the authority to accept the transferring of the repo and also grant the administrative role. |
Beta Was this translation helpful? Give feedback.
-
|
@esdandreu Hey, happy to accept the repo whenever you'd like to transfer it. I can definitely give you the admin role on that repo |
Beta Was this translation helpful? Give feedback.
-
|
I requested the repository transfer to @bashbunni. I tried to transfer it directly to |
Beta Was this translation helpful? Give feedback.
-
|
@esdandreu Awesome, I'll transfer it to the charm community on my end. Thanks so much! |
Beta Was this translation helpful? Give feedback.
-
|
@esdandreu Done! You have the admin role for this repository as well |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I made a small library with some connectors I needed to add Bubbletea components to an existing CLI: https://github.com/esdandreu/glitter
I found it difficult to add dynamic elements to existing CLI applications. It is particularly cumbersome if you already have a logging mechanism because logging can interfere with a dynamic element. Glitter solves this problem by becoming glue between a Bubbletea model and a logger's output.
I think it fits into Charm's ecosystem and I was wondering if you were willing to adopt it. I am willing to transfer ownership to https://github.com/charm-community. It probably doesn't meet your quality standards yet, but the package is rather simple so it shouldn't be a problem to improve it to meet your quality expectations.
Let me know what you think,
Andreu
Beta Was this translation helpful? Give feedback.
All reactions