- Do all your work in a public repository called
data-structures-and-algorithms
- fork this repository
- write all of your code in a directory named
trees
- push to your repository
- submit a pull request to this repository
- submit a link to your PR in canvas
- write a question and observation on canvas
Your lab directory must include
- index.js -- The entry point to your module
- README.md -- with a documentation about your lab
- .gitignore -- with a robust .gitignore
- .eslintrc -- with the class .eslintrc file
- .eslintignore -- with the class .eslintignore
- .package.json -- with all dependencies and dev-dependencies
- lib/ -- directory for holding your programs helper modules
- test/ -- directory for holding your programs unit and integration tests
- write at least three test assertions for each method of the Stack and Queue List Data Structures
- organize your tests into appropriate describe/it blocks for test output readability
- in your README, write documentation for you data structures
- your documentation should includes code block useage examples
- provide instructions for:
- installing and using your data structure
- accessing each method
- running your tests
- implement a Tree Constructor
- implement
insert(node)
andremove(node)
methods on the class - implement
find(node)
methods on the class - implement
serialize()
anddeserialize()
methods on the class- Why? You cannot simply use
JSON.stringify
andJSON.parse
because your tree will be made up of class instances. For that reason, you'll need to concoct a way to traverse the tree into a structure that you can run throughJSON.parse/stringify
. One idea might be to do a traversal, building up an object literal with all of the right references, or perhaps an in-order array that simply notes all of the node values and links...
- Why? You cannot simply use