Edge slice

[dpgraham4401]

Description

Separate the edge slice from our existing slices. With this, our store structure takes shape in a very manageable way.

we have the followign structure to our Decision Tree store. The Tree store has three sub-slices

1. Node slice. Manages the creation/removal of visible nodes on the tree
2. Edge Slice. Same as above but for edges that connect our nodes
3. Decision Slice. Act as a sort of database that we pull information from to create Nodes and Edges.

There is also a tree slice which is a shared slice (it depends on the above three slices) and unifies the logic, present a clean, abstracted, interface for working with the store.

for example, the tree slice has a showNode action which dispatches actions in the subslices to (1) create a node, (2) create an edge, (3) update our decision slice to reflect the user decisions.

Issue ticket number and link

Checklist

• I have added tests that prove my fix is effective or that my feature works
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings