David

The CLI currently accepts relative and absolute paths, such as: ``` $ aglint file1.txt file2.txt subdir/file3.txt D:\work\my-filters\filter.txt ``` In the future, we can supplement this with glob patterns, such as...

I suggest implementing debug mode. If we pass the `--debug` flag to the CLI, it should print everything to the console in detail so that the config building, scanning, walking,...

Currently, supported directive names, hints and platforms are [just burned](https://github.com/AdguardTeam/AGLint/blob/31c3ab68f2fddb8515451a762e899ad3c823529d/src/linter/rules/unknown-hints-and-platforms.ts#L18-L30) into these rules. It would be good to make them configurable, for example like this: ```yaml rules: unknown-hints-and-platforms: ["error", {...

I suggest considering the implementation of Coveralls integration. References: - https://coveralls.io/ - https://coveralls.io/github/badges/shields - https://github.com/marketplace/actions/coveralls-github-action

Currently, [`lint`](https://github.com/AdguardTeam/AGLint/blob/aee21dbcad3e2d07c054293a501cca071b07dfd7/src/linter/index.ts#L573) method only accepts raw filter lists as parameters, but it would be nice to improve it in such a way that it also accepts AGTree filter list nodes...

We should add `lint-staged` to the integration docs: https://github.com/AdguardTeam/AGLint/blob/master/docs/repo-integration.md Reference: https://github.com/okonet/lint-staged

Config file creation wizard

1

Currently we only have a very simple config file generator. In the future, we need to create a proper config creator wizard that will get the user's needs and the...

Example: https://github.com/csstree/csstree#top-level-api Related: https://github.com/AdguardTeam/AGLint/issues/43

Move linter rules descriptions from README to docs folder

2

@ameshkov I think it makes sense to move the descriptions of the linter rules from the README to the docs folder, as separate files. So the link would be https://github.com/AdguardTeam/AGLint/blob/master/docs/rules/adg-scriptlet-quotes.md...

Currently the test coverage is insufficient at certain points (50%, 70% etc), although the parser has been functionally tested in detail. We should extend the unit tests to achieve at...