Large lines which contain strings are miscalculated, because the tool removes the string contents before counting them.

Example:

137 characters:

sfab_FabricatedSObjectStub child1 = new sfab_FabricatedSObjectStub(Account.class, new Map<String, Object> { 'Name' => 'Foo-1' });

Exactly 120 characters if we ignore the two tabs, but still 128 characters:

sfab_FabricatedSObjectStub child1 = new sfab_FabricatedSObjectStub(Account.class, new Map<String, Object> { '' => '' });

Files like ClassName.cls-meta.xml are not ignored, and should be ignored.

List<User> users = [select Id, Email, IsActive from User where Id not in :ignoreIds];

returns the error: W0001 at 19: SOQL query with more than one condition and/or field being searched should be splitted into multiple lines.

^ Also there is a grammatical mistake in the error wording.

I'm really excited for this project but see it hasn't been touched in a while. Are you happy to accept pull requests on this repo?

Running in a single file the linting works, but when specifying a folder it does not.

📂 - Running on folder src/classes...
✅ - No errors found.

📄 - Running on file src/classes/OpportunityWS.cls...
❌ - 29: Line exceeds the limit of 120 characters.
❌ - 117: Line exceeds the limit of 120 characters.
❌ - 127: SOQL query with more than one condition and/or field being searched should be splitted into multiple lines.
❌ - 138: Line exceeds the limit of 120 characters.

Actual example:

202/491 (58.85947046843177%) passing

Round that to the scale of 2:

202/491 (58.86%) passing

Right now there's a list of errors, but no indicator of which file the error was found. Nothing to bother with when running on a single file, but is a big issue when running on folders.

• Be able to run the linter from the command line (should be a priority when getting more items done in this list)
• Make the linter read and sort the code by contexts.
• Make the linter able to distinguish between context types (class scope, method scope, etc).
• Basic rules with error outputs, like maximum line length.
• Detect SOQL statements used in one line
• Detect SOQL statements inside for loops as list variable:
  for (Object o : [SELECT ... ]) { ...
• Basic detection of SOQL statements inside loop structures.
• Create code for the different errors, and flags to ignore those when necessary.

Add a summary at the end of the report, like:

[37/40] - 5 errors found on 3 files.

Note: the left counter is for files, not errors. The error count can be bigger than the file count, since a file can have multiple errors.

Possibly add color to the output, like when running tests with Mocha. 🤔