CE-738: Refactor Tree Field Type

[MKwenhua]

Purpose
To allow nested tree fields/grouping and to simplify the TreeField datatype.
Make sure to read the extra details.

JIRA
https://careerbuilder.atlassian.net/browse/CE-738

Changes

• Improvements and fixes

  • TreeFieldType is now an actual tree as in it supports arbitrary nesting
  • Improved lookup and indexing
  • Will be much easier to render in React and update values.
  • TreeBuilder makes it easier to nest fields

• Changes to developer setup/environment
  *

• Architectural changes
  *

• Migrations or Steps to Take on Production
  *

• Library changes

  • Removed pomona

• Side effects
  *

Screenshots

• Before

• After
  

Feature Server

How to Verify These Changes

• Specific pages to visit
  *

• Steps to take
  *

• Responsive considerations
  *

Relevant PRs/Dependencies

• CE-738: Refactor Tree Field Type cortex-plugins-core#69

Additional Information

Ok first I would like to bring up TreeBuilder which I know you do not want to have any complex custom logic, but I assure you that I only built it so that creating the Tree data structure could be more accessible. It generates the tree field ids and makes nesting easier.

for example Below I create a two top level head nodes for the topic "Gaming Setup":

tree = TreeBuilder.new
tree.add_value('Desktop PC')
tree.add_value('Gaming Console')
tree.find_node('Gaming Console').add_value('MS')
tree.find_node('Gaming Console').add_value('Nintendo')
tree.find_node('Gaming Console').add_value('Playstation')
tree.find_node('Gaming Console').find_node('Playstation').add_value('PS3')
tree.find_node('Gaming Console').find_node('Playstation').add_value('PS4')

tree.tree_data

Besides the rake seeding task there TreeBuilder is never used again.

Also I added some example code with the function TreeBranchClicked for branch selections.

Note: There seems to be an elusive bug where the data for Categories seems to disappear during validations, which is why I removed them in this repo

[toastercup]

@MKwenhua unfortunately, this does not use RubyTree as we had discussed, so I don't know how much of this we can actually use. I like the resulting data structure you designed, but the business logic around it will need to be replaced with RubyTree before this can be merged. I'd suggest moving on to another story for now.

[toastercup]

Closing this for now - we will revisit next quarter.