Another, very legitimate example, would be diacritic characters in localized README (or other) files. Until UTF-8 support is not present in text linter, i simply have to disable linter for files that have words like "żółć" in them. Plus using ¯\_(ツ)_/¯ in doc would be beneficial to some 😉

Yes, but I is also reported by jsHint: https://github.com/jshint/jshint/blob/2.1.4/src/shared/messages.js#L195

jshint linter only allow W and E prefixes - https://secure.phabricator.com/diffusion/ARC/browse/master/src/lint/linter/ArcanistJSHintLinter.php;2234c8cacc21ce61c9c10e8e5918b6a63cc38fc8$145

cslint is deprecated, see T8978.

cslint is deprecated, see T8978 for more information.

This is also a duplicate of T4954, which was fixed by the addition of per-linter version support in D14298.

For reference and the benefit of people Googling how to configure a script and regex linter, here is a full example (using sass-lint):

We don't have enough information about this problem to design a solution, and haven't received more information in more than a month. See Describing Root Problems and Contributing Feature Requests for details on how to submit an actionable feature request.

I don't know RuboCop well enough to definitively answer the question about whether that mode exists, or to volunteer to maintain the driver. But I opened a parallel issue in the RuboCop repo, so hopefully we'll find out whether RuboCop has this mode soon enough.

Assuming this mode does not exist, the clearest pathway forward is for you or someone else to:

Does RuboCop actually have a mode where it emits errors and replacement text?

I've been avoiding those tools as compiling our project for .class files requires a lengthy amount of time, which would be better integrated into our jenkins test runners.

It does require .class files - I run it in the CI along with the tests (And PMD).

I thought FindBugs required analysis of the .class files which I didn't think would make useful for linting, but perhaps as UT or something?

Findbugs produces HTML, so I've made it into remarkup at https://github.com/avivey/remarkup-java (In Community Resources).

Resolved by D15019.

Added a proposed patch. See additional comments in the diff.

That shouldn't be a problem. I'll take a look at doing something later in the week, time permitting.

I'll upstream regex changes if they include unit tests.

Different (albeit related) bugs:

Looks like you are already aware of T8404, and this is a dup; Why did you submit another ticket?

This sounds awesome.

I renamed the task to indicate specifically which linters are being asked for, so as not to just request generic "Java" ones. Initially this task was just for checkstyle, but after I got it working in D14632 I decided to give PMD a shot as well. In hindsight it probably would have been beneficial to keep them separate, though there is a dependency on some changes in order to get a java jar to run as a linter. Let me know if you prefer them to be separated to different revisions/tasks.

In T10038#150709, @avivey wrote:

Basically all of this also applies to Unit binders, right?

In T10038#150629, @epriestley wrote:

Given how much of a backlog there is here and how slowly I've been able to move through it historically, my initial thought is that there may be no mid-term and T5055 is the pathway forward.

Although T5055 is a large amount of work, it helps us in the long term, while work against these issues directly does not, and I suspect T5055 is more like 10x more work than dealing with all this stuff directly rather than, say, 100x more work.

Basically all of this also applies to Unit binders, right?

One of my first thoughts was similar to @cburroughs', that developing phabricator extensions with the phabricator community could be helpful/fun. However managing that seems like it wouldn't come "for free" and would involve non-insignificant maintenance.

Do you see there being a "Blessed" foo-linter (maybe as a repo on this instance?), or will there be multiple foo-tributes fending themselves in the wilds of github?

Do you see there being a "Blessed" foo-linter (maybe as a repo on this instance?), or will there be multiple foo-tributes fending themselves in the wilds of github? At least one nice thing about having linters upstream is that you get to use phabricator (including arc lint!) to develop them.

Given how much of a backlog there is here and how slowly I've been able to move through it historically, my initial thought is that there may be no mid-term and T5055 is the pathway forward.