[SERVER-53526] libdeps visualizer: Remove all frontend state info from backend Created: 28/Dec/20 Updated: 25/Jun/22 Resolved: 24/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | Mitch Wagner (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Dev Platform 2022-06-27 |
| Participants: |
| Description |
|
Currently the back end has a concept of the frontend ends state via what nodes are currently selected. There might be other small tidbits of frontend state in the backend.
Originally the backend was used for relying state information between frontend components, but redux should be used for relying that information between components instead.
Theres not a real reason to do this, the backend should only analysis the graphs using an input from the frontend and then returning an output back to the frontend. This allows the back end to serve multiple front ends.
|
| Comments |
| Comment by Githook User [ 24/Jun/22 ] |
|
Author: {'name': 'Mitch Wagner', 'email': 'dev@mitchwag.com', 'username': 'mitchwag'}Message: |