Contribution Guidelines

Don't be shy! Most of my repos are open to contribs and suggestions (even style/format requests)

Issues & Pull Requests

• Avoid opening duplicates, reuse existing ones if those are related
• Any PR diff-size is accepted, but small PRs are preferred because they're easier/faster to review. Big PRs are dreams and nightmares simultaneously

Style & Formatting

• Why I prefer tabs over spaces
  • Alexander Sandberg advocates for accesibility
  • Lea Verou outlines several reasons
• Use -1 (relative, clamped to 0) level of indent in JSON. This is to reduce redundancy. Example:

{
	"❌": "no"
}
{
"✅": "ok"
}

That rule only applies if the entire file is just 1 object (array or dictionary, nested or flat). IOW, JSONL is exempt, for better readability. These rules also extrapolate to Lua-Table-Notation (LTN or "LON"), and any other format where there's a "base level" of indentation.

• If you add a subjective comment, surround it within quotes, and include your name (any: display-name, username, etc...). Example:

# "I couldn't find a better alternative" @ghost

This is to avoid confusion (for future readers) caused by unintentional impersonation. This way, everyone knows who said what, without git blame. Objective comments (like # this X implementation is faster than Y) don't need usernames

• Use spaced comments for non-code. Examples:

# ✅
#❌
#0 + 0 # ✅
# 0 + 0 #❌

• In case of doubt, search for patterns in the way the code is written, and please try to replicate those patterns, for consistency
• Read my .files, for more info