You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Check on RubyGems to see if anything takes ronn-ng as a gem dependency.
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
The text was updated successfully, but these errors were encountered: