Manage custom configuration sets (add/delete/load)

[ce-bo]

Feature request (raw)

Feature: Save current configuration. Add a button to the main menu (next to "scenario") that allows to save the current setting. It requires a setting name. As soon as saved the setting (redux state without the cc.json part - the latter is ) (simple + or "add" button next to an input field for the name) it's possible to jump back to that configuration / setting by clicking on the configurations name. Next to the configuration name there's a delete button (similar to the custom scenario ones). This is only kept in memory! Do not use the local storage.

Description

As an auditor, I want to be able to switch between preconfigured map configurations so that I can return to earlier states easily and switch back and force.

Acceptance criteria

• There is a button to open a menu which lists all currently saved configurations with its names next to "custom scenarios".
• There is another button inside the opened menu to add a new custom view ("+" label).
• The buttons show appropriate titles on hover.
• Inside the menu, I can delete individual configurations
• If a specific configuration is clicked, the configuration will be loaded and the map will be re-rendered.

Development notes (optional Task Breakdown)

• An API has to be defined as similar to the cc.json schema
• The API has to include the following parts initially:
  • Overall everything that is necessary to provide the exact view of the user later on
  • Excluded/Filtered/Blacklisted parts
  • Presentation mode and view settings
  • Current render mode (single/multi/delta)
  • Focused building
  • View angle
  • Zoom factor
  • Hash value of the map (a single configuration is always only valid for a specific map.)
  • used metrics and thresholds (colors) as well
  • distribution of a metric (e.g. rloc) per programming language
  • ....
• The API has to be versioned
• Configurations for delta and multiple mode are only valid in case that both maps are loaded and match the hash value.
• It may not be identical to the redux state as the redux state may change at any point of time
• Configuration name (optional: default is Map Name + increasing number)
• It is possible to add infinite configurations per map.
• We need a logic to transform the redux state and all it's necessary (API) information to a configuration and vice versa.
• The configuration should never include the metric data itself, just the metric types
• The data is saved in the Local Storage
• Mark configurations which are not mapped to the current map as disabled or rather hide them in a collapsed list.

Open questions

[ce-bo]

We have encountered a problem when setting the state and setting the camera position from the custom view afterwards, the camera position will be overridden by the default camera position.
This is due to the fact that events are processed without guaranteeing the order.