I added a DOM folder under scripts and added a utility folder in the DOM folder...
I also added nukeDom.js file which features two funs that clear the whole DOM and the other fun clears DOM by id.
Steps to Test
Put an id and text in the HTML
Run hs -o
Open dev tools
In the console log nukeDom() (this should clear the whole HTML)
Reload page
In the console log nukeElement("id") (this should clear only text within that id. Make sure you are passing the actual id of whatever text you are trying to clear and not the word "id")
Tell Jake he did a great job and to go ahead and merge this branch
git fetch --all
git checkout JCnukedomfun
Impacted Areas in Application
List general components of the application that this PR will affect:
Definition of Done
The project must be fully documented. This includes the following:
Complete README that documents the steps to install the code, how to install any dependencies, or system configuration needed.
Every class must be documented with purpose, author, and methods.
Every method must be documented with purpose and argument list - which itself must contain a short purpose for each argument.
The project must be able to run fully, and without errors, on each teammate's system.
Fulfills every requirement. Every line of code has been peer reviewed.
For projects that require unit testing, core functionality must be identified and have at least one test for each.
I added a DOM folder under scripts and added a utility folder in the DOM folder... I also added nukeDom.js file which features two funs that clear the whole DOM and the other fun clears DOM by id.
Steps to Test
git fetch --all git checkout JCnukedomfun Impacted Areas in Application List general components of the application that this PR will affect:
Definition of Done The project must be fully documented. This includes the following: Complete README that documents the steps to install the code, how to install any dependencies, or system configuration needed. Every class must be documented with purpose, author, and methods. Every method must be documented with purpose and argument list - which itself must contain a short purpose for each argument. The project must be able to run fully, and without errors, on each teammate's system. Fulfills every requirement. Every line of code has been peer reviewed. For projects that require unit testing, core functionality must be identified and have at least one test for each.