What is the problem you're trying to solve?

The developers on my team use class and id attributes in attribute selectors instead of using id selector or classname selector. This adds complexity and inconsistent coding style.

What solution would you like to see?

To fix the above mentioned problem, having this lintin

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"
}

At least I can't make sense of it:

warning: some ranges overlap
   --> pdf/src/primitive.rs:187:17
    |
187 |                 b' ' ..= b'~' => write!(f, "{}", b as char)?,
    |                 ^^^^^^^^^^^^^
    |
    = note: `#[warn(clippy::match_overlapping_arm)]` on by default
note: overlaps with this
   --> pdf/src/primitive.rs:186:17
    |
186 |                 b'"' => writ

Hi Web Hint Team,

I have just started using Webhint.io browser extension with both Firefox and Chrome and find it awesome. There is one thing which i think is absolutely required and that's a way to print (to pdf) / save the results generated.

I hope you will find this request genuine.

Regards,
Abhishek Jain

There's a formatting specification for Tag Keys and Values. One issue with applying some changes is that you are disallowed from using certain characters (notably the ,) in a Tag Value, and this is not being caught by tflint currently.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html#w2ab1c25c10d254c13c17

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>) 

I really like enforcing one expectation per example. But with RSpec's exception matching, you need two expect calls if you want to assert something about an exception:

expect { my_code }.to raise_error(MyErrorType) do |error|
  expect(error.message).to match /something went wrong/
end

There's no way to match against the error message without first wrapping the call, and RSpec o