Returns:

Invalid config file: Unexpected token } in JSON at position 210

for

{
  "threshold": 30,
  "identifiers": true,
  "literals": true,
  "color": true,
  "minInstances": 2,
  "ignore": "test|spec|mock",
  "reporter": "json",
  "truncate": 100,
}

should be:

{
  "threshold": 30,
  "identifiers": true,
  "literals": true,
  "color": true,
  "minI

1. Summary

It would be nice, if HTMLHint documentation will contain arguments, why HTMLHint users must use specific rules.

2. Argumentation

“Must” in The script tag can not be used in head., Id and class value must meet some rules: underline, dash, hump. is not argument. The documentation does not show the reasons. Users should know “Why must”?

3. Example of expected behavior

It would be great if anyone using code-forensics in a Windows OS could take a little time to write a little page to explain the main gotchas required to get the tool running in Windows. If you can contribute let me know and I will be happy to include your documentation in the current wiki.

This does not mean I intend to fully support Windows in the future, my intent is just to provide some hint

In https://xtdmake.readthedocs.io/en/latest/installation.html, see :

cd xtdmake-${tag}.tar.gz
mkdir .build
cd .build
cmake ..
sudo make install

Should be :

cd xtdmake-${tag}
mkdir .build
cd .build
cmake ..
sudo make install

User story

As an API producer and consumer,
I want to declare and store eslint-plugin-crc report options in a configuration
In order to commit standards to version control.

Acceptance criteria

• 1. All eslint-plugin-crc (alias crc) command-line Options can be serialized as:

• 1.1. JSON

  {
    "crc/report-output": "/path/to/crc-report.md",