I think there are many ways to participate in a community, and extending an existing gem is perhaps one of the best forms of flattery and respect.
Being silenced for merely announcing gem, which provides subjectively useful functionality to the users of the original gem seems surprising to say the least. And I still don’t know the actual reason.
I’m glad there is another community here, and hopefully my efforts to provide pluggable components to one of the existing gems will be seen as a positive contribution. The site provides attribution to all of the gems the plugins are built upon.
Hi @kigster — I’m very sorry about this! To my knowledge, this wasn’t an action any one of our team took directly.
Was this on the discourse.dry-rb.org forum? I’ve just checked there, and it looks like one of your posts got caught by Discourse’s automatic spam detection. It does things like this e.g. when infrequent posters come back after a long time and share posts with links, etc., which is probably what happened for yours.
It looks like a single post of yours got caught. I’ve marked the post as “not spam” and restored it now. Here it is.
If you ever have issues in any of our community spaces, you’re welcome to get in touch with us directly. You can email conduct[at]hanakai[dot]org, or even just message me directly on this forum, or in our Discord, where you can reach both me and our mods. We are always here to help.
Once again, sorry for the disruption around your post!
And while we’re here, another couple of thoughts:
My hope is to merge all the content the Dry and Rom forums into this one (Hanakai is the new home for all these projects), but this is a good reminder that I could at least look at setting up a notice to encourage people to come here instead.
Your Dry CLI extensions look really helpful! Nice work on those. We’re actively working on a 2.0 for Dry CLI right now, including built-in styled text support that we merged just last week. I’d love to colorise our default help text — would you be interested in starting a PR for this? I’m also still interested in working out some kind of first-party autocomplete solution, too. Those cover your dry-cli-{autocomplete,help} packages. The full surface area of dry-cli-ui is probably too big for us to bring into the gem itself — having an extension gem provide things like that makes a lot of sense. We may choose to bring one or two basic affordances into the main gem, though, like a progress bar.
Let me know if you’re interested in helping out Cheers!
Tim, thank you so much for clearing up what’s happened and your thoughtful and informative email. I would absolutely be interested in providing a PR to colorize and auto-wrap long descriptions for commands and subcommands, which is what dry-cli-help does. But that’s not all it does. Because it also adds the configuration section which allows you to declare gem’s title, description, and epilogue. Which are all obviously optional. But those are the features that I’ve hand-patched in most of my other gems.
I think that would make dry-cli much more presentable. Even though it’s quite presentable as is. I also completely in agreement that the heavyweight gem like the UI is best kept as a separate plugin. And I think the fact that Ruby allows you to simply pull in a gem like that and get all this functionality for free is a testament to Ruby’s flexibility and dynamic nature that we all come to love.
On another note, I see that you’re from Canberra, Australia. My family is in Melbourne and I spent six years there before moving to San Francisco. I still have my dual citizenship and go back there every now and then. I spoke at 2015’s Australia RubyConf. I guess we could have met there LOL. And maybe even had a beer!
Now, the autocomplete story is actually quite interesting. The gem that I published, dry-cli-autocomplete, its power and its limitation at the same time is the fact that it generates bash and zsh autocomplete functions once by statically walking through the commands, subcommands, arguments and options.
That makes it really fast to autocomplete, but it does make it impossible to do a dynamic real-time lookups. So if you added a command dynamically to your gem at runtime, the other gem that does auto-completion would fit you better because I believe that it does walk the tree every time you type the tab tab.
Thanks again, and glad to join such a stellar community.
These look like pretty cool tools but I think there’s a bit of overlap between these tools and what will be in the 2.0 release for dry-cli. Be sure to check the latest main for some of the changes we’ll be making.
Cheers!