AnyLint icon indicating copy to clipboard operation
AnyLint copied to clipboard

Lint anything by combining the power of scripts & regular expressions.

Results 22 AnyLint issues
Sort by recently updated
recently updated
newest added

At the moment, getting a good overview of all the rules within a config file is hard. Thereforew, it would be great if a different and more useful kind of...

Such a converter could transform this: ```yaml class_name_suffix_collection_view_controller: included: ".*\.swift" regex: 'class +\w+(?]+>)? *: +\w+CollectionViewController' name: "Class Name Suffix View Controller" message: "All `CollectionViewController` subclasses should end on `CollectionViewController`." severity:...

Setting up anylint in pre-commit hooks should be as easy as possible. Thus, adding a command like `anylint --hook` might make sense. The command should output the changes made, so...

## Problem Statement As it's in the name of AnyLint, it should be able to lint anything. This can also be understood in a way that AnyLint can start and...

enhancement

## Problem Statement The documentation is all in the README and lacks structure for different use cases. ## Suggested Solution DocC provides a good "GettingStarted.md" file and the option to...

enhancement

At the moment, we have 1 static template within the project, but instead we could build a template loading system, where different template portions could be combined to build a...

## Problem Statement Currently the only possible way to setup simple Regex-based lint rules is to write Swift code. While this allows a maximum of flexibility, it has drawbacks: 1....

enhancement

## Expected Behavior When I autocorrect a file path to a new path, the new path is created and the file is moved to it (unless the file already exists)....

bug

## Problem Statement Sometimes one needs a regular expression with exceptions. For example consider a regex that matches all literal numbers with 4 digits or more and reports a violation...

enhancement

## Expected Behavior The applied autocorrection report in the command line should give some context, even when the regex only maches only a very small portion of a line. ##...

bug