Skip to content

Only forcibly generate diagram files for report if missing - use custom diagrams in report #164

Only forcibly generate diagram files for report if missing - use custom diagrams in report

Only forcibly generate diagram files for report if missing - use custom diagrams in report #164

Triggered via pull request June 17, 2024 11:16
Status Failure
Total duration 18s
Artifacts

golangci-lint-action.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
lint: pkg/report/colors.go#L1
: # github.com/threagile/threagile/pkg/report
lint: pkg/report/generate.go#L81
config.OutputFolder undefined (type reportConfigReader has no field or method OutputFolder)
lint: pkg/report/generate.go#L81
config.DataFlowDiagramFilenamePNG undefined (type reportConfigReader has no field or method DataFlowDiagramFilenamePNG)
lint: pkg/report/generate.go#L88
config.OutputFolder undefined (type reportConfigReader has no field or method OutputFolder)
lint: pkg/report/generate.go#L88
config.DataAssetDiagramFilenamePNG undefined (type reportConfigReader has no field or method DataAssetDiagramFilenamePNG) (typecheck)
lint: internal/threagile/analyze.go#L8
could not import github.com/threagile/threagile/pkg/report (-: # github.com/threagile/threagile/pkg/report
lint: pkg/report/generate.go#L81
config.OutputFolder undefined (type reportConfigReader has no field or method OutputFolder)
lint: pkg/report/generate.go#L81
config.DataFlowDiagramFilenamePNG undefined (type reportConfigReader has no field or method DataFlowDiagramFilenamePNG)
lint: pkg/report/generate.go#L88
config.OutputFolder undefined (type reportConfigReader has no field or method OutputFolder)
lint: pkg/report/generate.go#L88
config.DataAssetDiagramFilenamePNG undefined (type reportConfigReader has no field or method DataAssetDiagramFilenamePNG)) (typecheck)
lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-go@v4, golangci/golangci-lint-action@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.