Expected behavior

When I have keys and values of a Hash aligned I should not see this offense in Rubocop report.

Actual behavior

Gist with larger example hash: https://gist.github.com/roolo/580b5061003355e07f631cffbe2fea9c

user:         current_user,
subscription: FactoryBot.create(:subscription,

When I have hash like this, I am told I should _elements of a hash

It would be nice to record some fancy GIFs for showing off ALE features in the README. We might want to update the main GIF too.

It might be good to use git gc or whatever for removing older binary files from the history, to make cloning fast enough, and consider hosting the images outside of the git repo.

from typing import NamedTuple


class A:
    def __init__(self) -> None:
        self.tuple2 = NamedTuple('x', [('y', str), ('z', bool)])

    def run2(self) -> NamedTuple:
        return self.tuple2(y='y', z=True)


print(A().run2())

The script will trigger "NamedTuple" not callable mypy(error), not sure if this is as expected

Reference:
https://mypy.readthedocs

Clearly describe the documentation issue

The CLI Docs instructs users to install stylelint with npm install stylelint --save-dev, and then suggests that, as a devDependancy, stylelint --help could be run.

Unless there's something wrong with my environment which is preventing the intended behaviour, I believe that for the CLI to work, users woul

Documentation under https://palantir.github.io/tslint/develop/custom-rules/ should be updated with an example using applyWithFunction instead of the old RuleWalker based example.

TODO

• Edit file: https://github.com/palantir/tslint/blob/master/docs/develop/custom-rules/index.md

When I run golang-ci on my dev workstation, I get a bunch of findings. When I run it inside our build docker container, I get far fewer findings, and no error code.

When enabling verbose output, I notice the "Packages that do not compile:" message, which only happens inside the container. There is no explanation why it won't compile, and no indication that some of the linters are not being ru

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

A user says:

Detects gender bias on 'chairperson' despite the term being the gender neutral alternative to gendered nouns.

Text that will trigger false positive: They thought the chairperson was interesting.

Affects PMD Version: 6.18.0

Rule: ApexCSRF

Description:
VisualForce Page fails when a controller's constructor executes DML queries. Salesforce seems to already protect against CSRF attacks.

Maybe I am missing something but there seems to be no security vulnerability, so this would be a False Positive.

H

This is a successor to #1915.
We should update the docs regarding the usage of type and symbol solving.

What do we need to update?

• --plugins path
• Under what conditions does type and symbol solving work?
• Which detekt integrations allow type and symbol solving to work. (CMD, Gradle, Maven...)

Question

Apologies if this has been asked before, but I'm curious what pylint considers a "block" and whether that could be documented more explicitly. Right now, the docs state:

add "#pylint: disable=some-message,another-one" at the desired block level or at the end of the desired line

Via neomake/neomake#790 (comment) I got the idea that we could have something like :NeomakeErrorformat <maker>, which would set the &errorformat.

Basically :let &efm = neomake#makers#…#maker()['errorformat'].

This is useful when running some maker manually, and/or using its output with :cbuffer etc.

Please hide context-menu "Lint this view" when "lint_mode": "background".
In this scenario that button does nothing. It uses up precious real-estate in the context menu.
I would do it myself but I don't know what the context-menu is_visible condition should be.
Thank you!