Douglas Eichelberger

Hi, I've noticed the type declarations are breaking the `yard` task, by discarding the annotations and emitting a bunch of warnings like: ``` [warn]: in YARD::Handlers::Ruby::DSLHandler: Undocumentable method, missing name...

Thanks for the quick reply, I’ll investigate further. Is it possible to organize `.yardopts` by cli command to avoid these warnings? Is it possible to bundle `doc` and `stats` as...

Ok, got it, I can work with that. The separation of concerns is maybe a bit non-intuitive here though. Since the output of `yard doc` includes stats, e.g. ``` Files:...

👋 I'm the author of the PR that caused the regression, thanks for flagging it @notEthan. Do one of you want to create a branch with a failing test? I'll...

:+1:

Hi, I think we can cut `string/inflections` too. Most of the time there is actually spent loading `i18n`, which we might only need in one place (`manpages.rb`), does that seem...

Is this still something we wan to pursue? I'd like to give it a shot if so.

Hi @yoheimuta, happy to sponsor the project! You've saved me a lot of time. With `all_default: true`, I do in fact see `ENUM_FIELDS_HAVE_COMMENT` violations. What I am trying to do,...

I took a quick stab at adding auto-disable support to custom rules (I'm new to Go, please be kind): https://github.com/yoheimuta/protolint/compare/master...dduugg:protolint:autodisable I got stuck trying to build the proto files though,...

This ticket is now low-priority, I wrote a quick wrapper to apply disables to existing violations: ```python3 #!/usr/bin/env python3 import json import subprocess def disable_protolint_violations() -> None: cmd = ["protolint",...