Fixes #285 - Resolve commented code sections

[cyrus-raitava]

Related Issue/Keyword:

285

Description:

The codebase contained a substantial amount of inexplicable, commented-out-code. To remedy this, an issue was opened to investigate into each found instance of commented code blocks without justification and decide whether they need to remain within the repository. A wiki page was introduced here, to explain what changes were made.

Testing:

Steps for manual testing: Testing for this will be mainly regression testing. This means checking that the project works as expected - removing commented code should in theory not change the way the project acts at all.

A tester should also read through the wiki page to see if they agree with the introduced changes, or not.

Thus, a tester should attempt to compare the functionality of the repo prior to this commit, and following the changes to this commit, with the actions under 'User Guide' in the wiki, here.

Checklist:

• [x] Latest master merged/rebased into your feature branch
• [x] Tests covering all changes
• [x] Meets the projects coding conventions
• [x] No out of scope changes
• [x] @Mentioned any relevant team members
• [x] No failure when running the linter (npm run lint)
• [x] Included a relevant gif (search here for inspiration)

[cyrus-raitava]

@hhagenson28 I have updated the wiki page and fixed the merge conflicts as requested, hopefully it's alright to merge now! 😄