MarketSquare/robotframework-robocop 1.8.0 on GitHub

A lot of new rules and changes - with huge number of contributions from others! 🚀
Some of the rules change names - see next section for more details.

Rule names changes

New rule for empty keyword or test case name (E0312 keyword-name-is-empty and E0313 test-case-name-is-empty) #337
New rule W1012 consecutive-empty-lines checking for more than consecutive_empty_lines = 1 empty lines #365
New rule W1013 empty-lines-in-statement checking for empty lines inside multi line statement #371
Tag rules now also parse tags defined in last line of documentation #194
New rule E0403 missing-keyword-name for calling variables without keyword name #386
New rule E1014 variable-should-left-aligned for ensuring that variables in variables section are left aligned #293

Enforce utf-8 encoding when reading file for RawCheckers to fix problems with different encodings (such as inccorectly calculcated length of line) #356
Fix invalid documentation regarding configuring format of the message #368
W1004 empty-lines-between-test-cases should now ignore templated tests #367
E0801 duplicated-test-case should now work correctly with normalized names #376
Robocop will now not show W1003 empty-lines-between-sections after keyword section if the number of lines is correct #382
format can be now used in .robocop configuraton file #387

When using invalid rule name Robocop will now throw exception listing close matches (if any) #358 #361
Allow to check only first word for capitalization in W0302 (wrong-case-in-keyword-name) #359
Documentation improvements #385

Special thanks for:

@rauttiz for reporting issues with line length checker
@MoreFamed that provided enhancement idea for our error handling and idea for optional configuration for 0302 rule
@bollwyvl for including our license inside our package
@d-biehl that dicovered issues when parsing test cases and keywords without name and also reported & fixed #376
@rdagum that reported issue invalid documentation for rule name inside format option and suggested ignoring some of the issues when parsing code with templated tests
@kvo-harmoney for idea of rule checking for consecutive empty lines
@yo-ga for adding parsing tags from last line of documentation and implementing rule for checking if variables inside variables section are left aligned
@j3n5h for reporting & fixing issue with detecting number of empty lines after keyword section
@Calletje234 for reporting issue with configuring format of output message in config file