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

Rename gem from "ronn-ng" to "ronn_ng" or the like? #84

Open
apjanke opened this issue Dec 31, 2022 · 0 comments
Open

Rename gem from "ronn-ng" to "ronn_ng" or the like? #84

apjanke opened this issue Dec 31, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request packaging
Milestone

Comments

@apjanke
Copy link
Owner

apjanke commented Dec 31, 2022

The RubyGems "Name Your Gem" guide says that "foo-bar" gem names are for when bar extends foo, and that non-hierarchical multi-word Gem names should use "foo_bar" with underscores instead. And that relates to the module namespaces used for them.

Should Ronn-NG change its gem name from "ronn-ng" (which looks hierarchical) to "ronn_ng" or something similar (which looks like a single name)? That would be more in line with the RubyGems naming convention, it looks like. But it would break backward compatibility, which would be bad. On the other hand, maybe not so bad: Ronn-NG is intended to be used just as a self-contained command, not as a gem library that other Ruby programs include.

TODO

@apjanke apjanke self-assigned this Dec 31, 2022
@apjanke apjanke added enhancement New feature or request packaging labels Dec 31, 2022
@apjanke apjanke added this to the 0.11.0 milestone Dec 31, 2022
@apjanke apjanke added this to ronn-ng Jan 4, 2024
@apjanke apjanke moved this to Low priority in ronn-ng Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request packaging
Projects
Status: Low priority
Development

No branches or pull requests

1 participant