As per angularsen/UnitsNet#328 (comment)

Having a set of tests to validate that the correct abbreviation notations and symbols are used would be helpful, as we have seen from before that discrepancies tend to creep in over time.

See #328 for the (currently work in progress) guideline, go through the comments and identify what tests to write for the guid

🐛 Bug Report

• tslint-to-eslint-config version: 2.3.0
• ESLint version: 7.24.0

Actual Behavior

"variable-name": [
  true,
  "ban-keywords"
]

is converted to

"id-blacklist": [
  "error",
  "any",
  "Number",
  "number",
  "String",
  "string",
  "Boolean",
  "boolean",
  "Undefined",
  "undefined"
]

Expected Behavior

id-blac

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene