Key Event Handling in KMP Solved! recently made a...

# feed

[Farhaan Shaikh]

Key Event Handling in KMP Solved!

recently made a KMP/compose multiplatform solution for key event handling so feel free to check it out! I want to first get the bugs figured out before I add more features like joystick overlay/controller joystick handling. I also want to get my library featured on kmp-awesome so I would appreciate getting to 50 stars on my repo, thanks for checking it out and your welcome for the library.

Library: https://github.com/Loop312/compose-keyhandler

[Stefan Oltmann]

Since when do you need 50 stars to be part of kmp-awesome? 🤔
Just send a PR.

[Stefan Oltmann]

I want to first get the bugs figured out before I add more features like joystick

Just an idea / hint: If you have known bugs, maybe release the first version of your lib as 0.1.0 and go from there. Let the version 1.0.0 be something special. That's my usual strategy.

[Farhaan Shaikh]

kmp-awesome says it under contribution (point 4) of the Readme

the v1.0.0 was a complete rewrite of the library to use DSL (which could've potentially introduced bugs)

[Konstantin Tskhovrebov]

awesome-ness is not about a count of stars but about community satisfaction and provided value

[Stefan Oltmann]

Ah, in fact I didn’t see the contribution guide at the end of the page before. 😅
My library made it into the list with less stars back then, so I guess I got lucky. 😄

[Stefan Oltmann]

My point was if this is experimental/beta/incomplete, let it be something below „1.0.0“, because that version number communicates completeness / maturity.

Ashampoo Kim is a port of the metadata part of Apache Commons Imaging and started out at v0.1 … it’s not yet 1.0.0, because there are things I like to improve first. It’s already in production and has no known bugs, but here and there are performance issues I want to tackle.

Ashampoo XMP Core is a Port of Adobes XMP Core… Because I wasn’t sure if I introduced bugs with the port I started out as 0.1, too. And there were minor things I fixed and convenience methods I added. After it was used in production for 6 months (or a year?) with no known bugs I finally declared it as 1.0.0 - this communicates „it’s done and you can use it in production“.
The versions after that were mostly library updates and some additional convenience methods.

[Stefan Oltmann]

In the history I see 1.0.0 is not the first version. Ok.
So what I would have wanted to suggest is declare it as v0.9 if it’s not battle tested.

Sorry, I’m way to wordy today. 🙈

[Farhaan Shaikh]

I see... this is the first library I created so I didn't really know all that much, thanks a lot for the wordy explanation (i appreciate it a lot actually), so what do you think i should do now, my original plan was to put any fixes as v1.0.X releases but I'm not exactly sure what to do anymore

[Stefan Oltmann]

Yes, you can’t take back maven central publications - so fixes will be v1.0.X

Maybe you are lucky and don’t need any 🙂