chavacava

Hi again @Groxx , I've reproduced the bug and after analysis, I confirm that the problem's root is the lack of type information about the variable `shardId`. As you can...

`revive` collects type information by using the `Config.Check` function from the `go/types` library . This function, with the advent of modules, was somewhat deprecated in favor of `go/packages` in the...

Hi, now you can configure file exclusions at rule level. Check #857 (yes, soon we will need a linter for the `revive` configuration :smile: )

Hi @mfederowicz if you plan to go ahead with the renaming, your PR are welcome. That said, the next phase of refactoring might imply breaking changes. Thus, before putting some...

Hi @feldgendler, thanks for commenting in this thread. Rules requiring type information introduce some performance degradation thus we try to keep rules _type free_ At the time we decided to...

Yes, and yes

I've rebased the branch #415 and now the rule does not warn on empty blocks on channel draining ranges. @feldgendler you can try the fix and let me know if...

Duplicated of #912

Yes, sure!

Hi @sk-, thanks for reporting the issue. I've developed the rule with the `else-if` interpretation described by @denisvmedia because I consider `else-if` constructs are indeed nested structures. The rule being...