VrpSetup refactor needed about solverstack-web HOT 2 CLOSED

Main goals refined:

1. Module setup form components should generally be implemented as agnostic parent components for module components.
2. Each setup form should control its states as well as optimized utilization of its child components.
3. Initially components will be grouped into domains for simplifying the early development process -- first of which are bundled under the Vrp Domain.
4. VrpBubbleMap should be a parent component of:

• MapAtlas
• MapLine
• MapCircle

5. The controlling forms should follow immutable property management, cascading state data into each child component. Components can potentially be keyed to optimize the utilization of d3.
6. Projection type should be defined by the parent form component.
7. Data types should be defined for the vrp domain to force component definition and utilization.
8. Things like shape scaling, color choice, etc. should be handled by the parent form component.
9. Resizing of the svg and its components should be controlled by the parent form.
10. Hover-text should be a default opt-out feature defined at the MapCircle component.

NOTE: this is an incomplete list. Not everything in this list should or will be implemented for the MVP. This list should be used as a general design guideline moving forward. Revisions are expected.

from solverstack-web.

completed basic refactor but need to do the following in the short-term:

1. add styling to child components of Vrp setup
2. add responsive resizing to Vrp setup
3. add hovertext
4. improve performance of refactor by doing mvp-worthy of the following:

• merging origin lat and lon onOriginUpdated & smarter checking
• general method implementations

5. improve readability and molecularity

from solverstack-web.