Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

linter should suggest spdx license string names or warn on them

See original GitHub issue

Issue:

Environment (conda list):

$ conda list

Details about conda and system ( conda info ):

$ conda info

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

scopatzcommented, Nov 8, 2019

I think we should have these in the documentation before we lint against them

0reactions

beckermrcommented, Nov 9, 2019

I don’t feel strongly on this. I’m happy to use them if we can but otherwise not.

Top Results From Across the Web

Linters | golangci-lint

Name Description Presets Since asasalint ⚙️ check for pass any as any in variadic func(...any) bugs 1.47.0 bidichk ⚙️ Checks for dangerous unicode character sequences...

SPDX License List | Software Package Data Exchange (SPDX)

Full name Identifier OSI Approved? BSD Zero Clause License 0BSD Y Attribution Assurance License AAL Y Abstyles License Abstyles

reuse-tool/CHANGELOG.md at main - GitHub

Better suggestions for faulty SPDX license identifiers in download and init (#416) ... The linter will complain about them, however.

"SPDX license identifier not provided" warning - Stack Overflow

It's a warning, not an error. So you are able to compile the contract without the license identifier, and it has no effect...

Release 1.0.0 Free Software Foundation Europe

First, read the REUSE tutorial. In a nutshell: 1. Put your licenses in the LICENSES/ directory. 2. Add a comment header to each...