Skip to content

Bug Report: code check call.Err !=nil but return a nil value error err #3012

@alingse

Description

@alingse

Summary

do you mean return call.Err or just return nil to ignore the call.Err ?

Steps To Reproduce

Expected behavior

Environment

  • OS: [e.g. Mac OS X High Sierra, Ubuntu 18.04, Windows 10, ...]
  • OS version: [uname -a]
  • gopass Version: [gopass version]
  • Installation method: [e.g. from source, brew, gopass repo]

Additional context

I create a linter to detect code that returns a non-relevant nilness error bug. I checked the top 1000 GitHub Go repositories and found this, all result listed in alingse/sundrylint#4

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugDefects

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions