I've started running the up-to-date version of awesome-lint from #29 on various well-known awesome lists and want to clarify some common edge cases.

Should the following scenarios be considered valid?

Awesome Rules

awesome/toc

The "Related Lists" section isn't in the table of contents. Should I add this to the blacklist of section names such as "License" and "Contributing"?

awesome/list-item

These all error because they don't end with proper punctuation. One option would be to relax this rule to only end with proper punctuation if the last character is in a certain ascii whitelist set.

• sparkly - Generate sparklines ▁▂▃▅▂▇

• cat-ascii-faces - ₍˄·͈༝·͈˄₎◞ ̑̑ෆ⃛ (=ↀωↀ=)✧ (^･o･^)ﾉ”

• why-is-node-running - Node.js is running but you don't know why?

awesome-nodejs uses sub-lists in some parts, whereas other lists use sub-headers (### Promises) to separate related content. Should we allow these types of sub-lists?

• Promises
  • Bluebird - Promise library with focus on innovative features and performance.
  • pify - Promisify a callback-style function.
• Observables
  • zen-observable - Implementation of Observables.

Third-Party Rules

no-literal-urls

• humanize-url - Humanize a URL: http://sindresorhus.com → sindresorhus.com.

(Edit Aug 10 2018: removed multiple edge cases that we already support)