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
Kebab the public interface #29
Comments
|
Consistency is the key thing, whichever way it goes. I'd be happy enough if it consistently used kebab-case; it seems to be what many things are settling on. |
|
I've just started to work on a GTK::Simple::RadioGroup widget. |
|
Cool. I'm working on a couple of things but it shouldn't get in your way, I'll probably get the #28 in today which you might want to bear in mind, but it won''t stop you doing what you want to do. |
|
I've done #28 now, so you may want to merge the current master before proceeding. Hopefully the way that the property facade I have implemented works is clear enough without any further explanation, if not give me a shout. |
|
To go back to the original question, there are only 10 public methods that are named in snake case - I'm minded to rename and deprecate the old names without further ado. |
Parts of the public interface are using
snake_casewhile I have been adding the new stuff withkebab-case, obviously consistency would be better and I think that the consensus has largely converged on usingkebab-casein new code.Obviously this would be an in-compatible change so there would need to be a short deprecation cycle (though as it currently stands the module isn't properly versioned so this in itself is somewhat problematic,)
I'll leave this for discussion for a bit before I do anything.
The text was updated successfully, but these errors were encountered: