golangci-lint/pkg/exitcodes/exitcodes.go

package exitcodes

const (
	Success = iota
	IssuesFound
	WarningInTest
	Failure
	Timeout
	NoGoFiles
	NoConfigFileDetected
	ErrorWasLogged
)

type ExitError struct {
	Message string
	Code    int
}

func (e ExitError) Error() string {
	return e.Message
}

var (
	ErrNoGoFiles = &ExitError{
		Message: "no go files to analyze",
		Code:    NoGoFiles,
	}
	ErrFailure = &ExitError{
		Message: "failed to analyze",
		Code:    Failure,
	}
)
Fix #78: log all warnings 1. Log all warnings, don't hide none of them 2. Write fatal messages (stop analysis) with error log level 3. Remove ugly timestamp counter from logrus output 4. Print nested module prefix in log 5. Make logger abstraction: no global logging anymore 6. Refactor config reading to config.FileReader struct to avoid passing logger into every function 7. Replace exit codes hardcoding with constants in exitcodes package 8. Fail test if any warning was logged 9. Fix calculation of relative path if we analyze parent dir ../ 10. Move Runner initialization from Executor to NewRunner func 11. Log every AST parsing error 12. Properly print used config file path in verbose mode 13. Print package files if only 1 package is analyzedin verbose mode, print not compiling packages in verbose mode 14. Forbid usage of github.com/sirupsen/logrus by DepGuard linter 15. Add default ignore pattern to folint: "comment on exported const" 2018-06-13 22:37:48 +03:00			`package exitcodes`

			`const (`
dev: clean up and used iota for exit codes (#2366) 2021-11-18 21:52:21 +03:00			`Success = iota`
			`IssuesFound`
			`WarningInTest`
			`Failure`
			`Timeout`
			`NoGoFiles`
			`NoConfigFileDetected`
			`ErrorWasLogged`
exit with the code 5 if no go files to analyze 2018-08-17 20:49:59 +03:00			`)`

			`type ExitError struct {`
			`Message string`
			`Code int`
			`}`

			`func (e ExitError) Error() string {`
			`return e.Message`
			`}`

			`var (`
			`ErrNoGoFiles = &ExitError{`
			`Message: "no go files to analyze",`
			`Code: NoGoFiles,`
			`}`
Fix staticcheck panic on packages that do not compile The bug was introduced in golangci-lint when migrating staticcheck to go/packages. Also, thanks to pkg.IllTyped we can analyze as max as we can by staticcheck. Relates: #418, #369, #429, #489 2019-04-21 10:33:39 +03:00			`ErrFailure = &ExitError{`
			`Message: "failed to analyze",`
			`Code: Failure,`
			`}`
Fix #78: log all warnings 1. Log all warnings, don't hide none of them 2. Write fatal messages (stop analysis) with error log level 3. Remove ugly timestamp counter from logrus output 4. Print nested module prefix in log 5. Make logger abstraction: no global logging anymore 6. Refactor config reading to config.FileReader struct to avoid passing logger into every function 7. Replace exit codes hardcoding with constants in exitcodes package 8. Fail test if any warning was logged 9. Fix calculation of relative path if we analyze parent dir ../ 10. Move Runner initialization from Executor to NewRunner func 11. Log every AST parsing error 12. Properly print used config file path in verbose mode 13. Print package files if only 1 package is analyzedin verbose mode, print not compiling packages in verbose mode 14. Forbid usage of github.com/sirupsen/logrus by DepGuard linter 15. Add default ignore pattern to folint: "comment on exported const" 2018-06-13 22:37:48 +03:00			`)`
No results found.