Idea for refactoring

[Mokhyy]

Hi Dev,

What do you think about modeling the keyboard parameters?
I feel like the codebase is growing and becoming increasingly tangled and messy.

I think it might be better to replace the old way of handling the keyboard , with different data classes and sealed classes.

For example, there are some files that currently hold the keyboard parameters using the old Java approach, such as:

• java/helium314/keyboard/keyboard/internal/KeyboardParams.java
• java/helium314/keyboard/keyboard/internal/KeyDrawParams.java

Of course, switching to data classes and sealed classes would likely require a major refactor, but it would prevent the code from becoming a mess and make future development much easier

[LeanBitLab]

Hi Dev,

What do you think about modeling the keyboard parameters? I feel like the codebase is growing and becoming increasingly tangled and messy.

I think it might be better to replace the old way of handling the keyboard , with different data classes and sealed classes.

For example, there are some files that currently hold the keyboard parameters using the old Java approach, such as:

• java/helium314/keyboard/keyboard/internal/KeyboardParams.java
• java/helium314/keyboard/keyboard/internal/KeyDrawParams.java

Of course, switching to data classes and sealed classes would likely require a major refactor, but it would prevent the code from becoming a mess and make future development much easier

planning to make the code cleaner, lets start from somewhere and fix one at a time