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,

I want to use eslint's autofix to fix layouts only.
Like this: eslint --fix --fix-type layout
(--fix-type: https://eslint.org/docs/user-guide/command-line-interface#fix-type )
To work that one plugin's rules must contains the type field.
( the type field: https://eslint.org/docs/developer-guide/working-with-rules#rule-basics )
Are there any reasons why this field cannot be added?

Hey. Just a question. Can we add possibility to extend from single string not just from array? So it will work like other linting libraries (eslint, stylelint, etc.).

package.json

"babel":  {
  "extends": "shared-tools"
},
"commitlint": {
  "extends": [
    "shared-tools"
  ]
},
"eslintConfig": {
  "extends": "shared-tools"
}

As suggested in the non_exhaustive RFC, when using non-exhaustive enums and structs in patterns, the lint would warn the user for missing variants or fields despite having a wildcard arm or a rest pattern.

This can be useful when new fields/variants are added by the upstream crate so that they don'

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?

Hi Coala maintainers,

Can you help clarify AGPL coverage in Coala's case? Specifically, are the modifications made by Coala, which would get put into the input source code, covered by AGPL?

Your clarification will help evaluate the technology selection. I'd be helpful If you could clarify your interpretation in the Q&A page.

Thanks,

Brian

🐛 Bug report

Description

When I run a scan against a very long URL, word wrap breaks in the results.

Environment

• webhint version: 1.2.1
• Browser version: Edge Beta (80)

reviewdog/reviewdog#405 introduced the -tee option, but there is no mention of the feature in the readme. This would be helpful info for us who are trying to implement/debug this tool

It would be fantastic if bad anchor-style links were detected and warned.
I wouldn't expect bad external URL links to be caught.

Current

export declare type TextlintRuleReportHandler = {
    [P in ASTNodeTypes]?: (node: TypeofTxtNode<P>) => void | Promise<any>;
} & {
    [index: string]: (node: any) => void | Promise<any>;
};
/**
 * Textlint rule reporter function
 */
export declare type TextlintRuleReporter<T extends object = {}> = (context: Readonly<TextlintRuleContext>, options?: TextlintRuleOptions<T>) 

There is a large warning for the resource aws_iam_policy_attachment to use aws_iam_role_policy_attachment instead.

I'd like to prevent the first resource from getting into our infrastructure with an appropriate tflint rule. We could mak

Prerequisites

• [y] Have you tried launching atom . from the terminal in your project's directory?
• [y] Have you verified the output from go env is correct? If it is, please include the output in this issue.
• [y] Have you updated Atom to the latest version?
• [n] Have you tried using Atom Beta, which can be run side-by-side with Atom Stable? Is the behavior

If you want your multi-document yaml files to look like:

1
---
2
---
3

You might think it reasonable to use document-start: {present: false}, but unfortunately this throws an error for each of the --- - even though there's no other way to express the file.

The section about the number of files found reports 0/0 for one of the other tools and the text following claiming a small difference between rmlint and fdupes does not match up with the data shown (the numbers are equal).

This is just an initial though, anyone is welcome to participate in this thread. Only once the format is finalised will I add this to Milestone.

Description
A user shouldn't have to head to the docs to view a list of rules (along with detailed description, parameters supplied, autofix availability). The CLI should allow this.

Use case
Much faster & more convenient for user because

You might accidentally use setlocal modelines=0, assuming that this would be a local option, but then it sets the global option instead.

Therefore it would be nice if vint could warn about this.

When using include_examples a new RSpec context is not created, unlike with it_behaves_like. It is a common mistake to write something like:

include_examples 'my thing' do
  let(:a) { 'a')
end

include_examples 'my thing' do
  let(:a) { 'b')
end

And the author of the test might not realize that a will be defined as 'b' in both cases. (NOTE: I'm writing this sa

The example which provides sample code for using gulp-nodemon with "React, Browserify, Babel, ES2015, etc." uses the NPM package gulp-file-cache which is no longer under development (pgherveou/gulp-file-cache#1). The example should be updated to use a package which is under active development.

We don't say anything in particular about:

• 412 (test to see if it's true, alert if not)
• 416 (test to se if it's true, alert if not)
• 417 (explain, alert if it's 100-continue)

... in status.py

The spotbugs migration guide suggests to replace com.google.code.findbugs:annotations with net.jcip:jcip-annotations:1.0 and com.github.spotbugs:spotbugs-annotations:4.0.0-beta1.

When doing so on a project, that uses spotbugs, the lint plugin fails with

undeclared-dependency