feat: added linting to the project

[Anush008]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Description

This PR proposes the following changes:

• Adding ESLint to the project. The linting rules are based on https://github.com/open-sauced/hot/blob/beta/.eslintrc.cjs, along with run scripts for linting (lint) and auto-fixing errors (lint:fix). 1c48e95.
• Resolves automatically-fixable errors with --fix. 0570c3e.
• Manual resolution of the rest of the linting issues. bcd1f47 0b61319 b7b3a3e. Refactoring to conform with linting recommendations.. 5c12058 93e741a 0eb064d.
• Additionally, this PR also addresses a bug with the wrong value being passed in createHtmlElement.ts. c175343.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Not applicable.

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 docs.opensauced.pizza
• 🍕 dev.to/opensauced
• 📕 storybook
• 🙅 no documentation needed

[diivi]

I'd prefer an unsquashed commit history with just 2 commits - one for the config changes and one for formatting. This is the general convention for formatting changes, so it's easier to see what was changed. Also, consider adding the commit where the code formatter actually runs to .git-blame-ignore-revs

[Anush008]

I'd prefer an unsquashed commit history with just 2 commits - one for the config changes and one for formatting. This is the general convention for formatting changes, so it's easier to see what was changed. Also, consider adding the commit where the code formatter actually runs to .git-blame-ignore-revs

Right. I'll try doing that.

[Anush008]

@diivi, I've overwritten some changes that can't be undone in my local. I'll re-open the PR with your suggested changes.

[bdougie]

@diivi, I've overwritten some changes that can't be undone in my local. I'll re-open the PR with your suggested changes.

Anything is possible to unwrite with git reflog. Just for a note for the future.