https://eslint.org/docs/rules/use-isnan

This is a proposal to modify the use-isnan rule.

Current rule setting:

use-isnan: "error"

Proposed rule setting:

["error", {"enforceForSwitchCase": true}]

The switch statement internally uses the === comparison to match the expression's value to a case clause.
Therefore, it can never match _case NaN. Also, `swit

For new checks and feature suggestions

• shellcheck.net (i.e. the latest commit) currently gives no useful warnings about this
• I searched through https://github.com/koalaman/shellcheck/issues and didn't find anything related

I can't check shellcheck.net because it requires JavaScript.

Here's a snippet or screenshot that shows the problem:

#!/bin/sh
set +x

Documentation for capIsNewExceptionPattern says the following:

allows any uppercase-started function names that match the specified regex pattern to be called without the new operator.

However, the actual behaviour seems to be that entire call expression is matched against the pa

Is your feature request related to a problem? Please describe.

This is a request for new cop based on @bbatsov's comment here.

Describe the solution you'd like

The cop should check for explicit parens when operators with varying precedence are used in a statement.

# bad
a && b || c
10 + 20 * 3

Information

VIM version

NVIM v0.4.3
Build type: RelWithDebInfo

Operating System: Ubuntu 18.04.4 LTS

ALE version:

commit 36e5337e30095afb10d02ef2ae362c8d6055e70d
Author: Horacio Sanson [email protected]
Date: Tue Apr 21 13:36:57 2020 +0900

What went wrong

When I enabled virtualtext cursor in my init.vim configuration (let g:ale_virtualtext_cursor = 1). For some

I'm currently trying to type an API using the signal module. At some point, we pass a callback that has the type signal._Handler (see: https://github.com/python/typeshed/blob/master/stdlib/3/signal.pyi#L73), which is not in the signal module, but in typeshed.

If I try to import it, I get an error, and I could not find the proper way to do so in the documentation.

Clearly describe the bug

"false-positive" no-descending-specificity with "empty" definitions (see below)

Which rule, if any, is the bug related to?

no-descending-specificity

What code is needed to reproduce the bug?

    nav {
      display: inline-block;
      a {
        display: inline-block;
      }
    }

    a,
    button,
    label {
      &:focus,

The README.md contains a lot of advanced config examples for functional tasks. We should probably add some basic ones as well:

1. '*.js': ['eslint'] <- fail when eslint finds issues issues
2. '*.js': ['eslint --fix', 'git add'] <- automatically fix eslint issues, and add to commit
3. '*.js': ['prettier --list-different'] <- fail when prettier finds issues
4. `'*.js': ['prettier --write

As you may have read in this blog post, we plan to deprecate TSLint in 2019 and support the migration to ESLint as the standard linter for both TypeScript & JavaScript. This will not be an immediate deprecation; on the contrary, there is a lot of work to do to ensure a smooth transition to the new tooling without any regressions. There are

Thank you for creating the issue!

• [ x ] Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
• [ x ] Yes, I've searched similar issues on GitHub and didn't find any.
• [ x ] Yes, I've included all information below (version, config, etc).

This isn't a bug, just a wishlist item.

Internally golangci-lint checks for a FAIL_ON_WARNINGS e

Since ESLint doesn't let us disable auto-fix for individual rules, and the capitalized-comments rule, while useful, can be annoying in editors when "auto-fix on save" is enabled.

SamVerschueren/vscode-linter-xo#78 (comment)

I would love to have fail_fast configuration option on check level not only at the level of the whole configuration file.

The use case I have in mind - i have one specific pre-commit check that performs docker builds of images that are used by later checks. This is fairly complex build and I have some optimisations in place to build it once and not re-run Docker build . again (because just run

• This is a bug report
• I searched existing issues before opening this one

Expected behavior

No warning.

Actual behavior

• Double quote to prevent globbing and word splitting.
• d is referenced but not assigned.

None of these are relevant. ShellCheck is never relevant, because it's all about how you run shell commands, while the json-array format doesn't run any s

Subject of the issue

Since there's a correlation between [get-alex/alex][alex], [words/cuss][cuss] and [retextjs/retext-equality][equality], we need some help updating the [contributing.md][contributing] file adding internationalization steps.

As mentioned in #202, the follow steps need to be specified on the file:

• The words and their respective rates need to be added to the [words/

I'd like to use ktlint's jar for a Kotlin program to format source code strings (my program accepts runtime Kotlin source via JSR223). I wasn't able to find documentation, or an example.

Can you direct me?

Environment

• Credo version: 0.8.5
• Erlang/Elixir version: 1.5.0
• Operating system: Windows 10 (build 15063)

Special characters (arrows, edge) display as garble

It seems configurations for proselint are centralized to different canonical files (namely $XDG_CONFIG_HOME/proselint/config, ~/.config/proselint/config and ~/.proselintrc) instead of a per project config basis.

So may I ask how to specify project/folder/files-specific rules? Maybe including some examples in the README.md would be nice?

Thanks

Write an article (possibly interactive) on tuning staticcheck's performance. With our new runner (to be committed), memory usage and CPU time behave as expected when you increase the number of processors:

• memory usage grows linearly
• runtime is inversely proportional
• speedups approach an upper limit as per Amdahl's law

If we let staticcheck measure and output the proportion of linear

I was working through setting up detekt in a sample Android project, and ran into some odd/confusing behavior. This occurred with version 1.6.0, but also seemed to occur if I tried older versions as well.

I set things up in my root level project as per the instructions here, and applied the plugin to my mai

Affects PMD Version:
All.

Rule:
ImmutableField

Description:

"Identifies private fields whose values never change once object initialization ends either in the declaration of the field or by a constructor. This helps in converting existing classes to becoming immutable ones."

Immutability, by defini

Steps to reproduce

With the following example code i encounter warnings that should not pop up.
It does not seem to be fixed i

The in-progress dev docs have a section on developer workflow: https://google.github.io/pytype/developers/index.html. We also have https://github.com/google/pytype/blob/master/CONTRIBUTING.md. They read like standalone docs with no knowledge of each other and contain different, occasionally overlapping (but at least not contradicting, I think) information. We should coordinate them in some way so

@alexeagle mentioned that the TS style guide has lots of documentation, but it doesn't seem like any of that is available here.
The most common issue we run into is type coercion. Apparently this is what the docs for that should say:
TypeScript code may use the String() and Boolean() (note: no new!) functions, string template literals, or !! to coerce types.

const bool = Boole

unit test coverage is always 0% , even the log shows that "Linter:UnitTest over".

command:
goreporter -p ./ -r /Users/jeffrey -f html
log:

2018/11/11 19:33:45 The template path is not specified,and will use the default template
2018/11/11 19:33:45 There are no packages that are excepted, review all items of the package
2018/11/11 19:33:45 Linter:CountCode over,time consumi

There are several issues open that suggest that it is unclear how Bandit is meant to be executed. In fact, there are no usage instructions at all in the Bandit docs.

Describe the solution you'd like

There should be simple, crisp, usage instructions in the Bandit docs, e.g.

Install Bandit:

pip install bandit

Run Bandit o

Since BS v3.4.1 and v4.3.1 we enabled sanitization for Tooltips and Popovers, so it would be interesting to add a warning if Bootlint detect sanitize at false

/CC @XhmikosR and @Herst