version 0.4 - rules improvements and bug fix
changed the format of rules to move the 'operation' field before the 'area' and 'id' fields - i.e. '[!][{+-=}][<area>][:<id>]' replaces the previous '[!][<area>][:<id>][{+-=}]' as well as making the rule syntax clearer, this change fixes a problem where a '-' could not be used in the 'action' field - previously this was not allowed as the regexp for that did not match '-' but, when it was added, caused the regexp to match it as an 'operation' moved the code to read in rules from a file from the main module to the the ConfigElementRules class as read_rules(), extending it to support comments in files with a leading '#' and skip blank lines
Loading
Please register or sign in to comment