[CONSOLE] UI errors in Map view

[MidnightLightning]

Overview

User story: As a visual learner who wants to understand the streams coming in and out of an address, I want the "map" view to be as understandable as possible, with no visual distractions that would hamper my understanding of the visualization. I want as clean a visual as possible to be able to screenshot it and share with others as an explanation for what's happening with my or their wallet.

User Persona/Target Audience: Visual learners who wish to use and share the Map view to explain the current state of streams to/from an address.

Deadline: ??

UI/UX Design:

The central node of the graph has extra links both top and bottom that appear to be connecting the central node to themselves. Those are not needed and visually distracting from the other connections.

• The attribution to React Flow in the bottom right (green circle) is not legible (color is same as background); should either be legible or removed entirely.
• Outflows don't space themselves out as the in-flows do (blue separations between nodes are different). The outflows being so close together makes the labels for those flows overlap (orange circle). To fix this, the outflows should be spaced out as the in-flows are.
• The central node is not centrally-aligned to either the in-flows nor out-flows horizontally. This makes a pretty unbalanced diagram overall.
• Nodes that are on the out-flow side have a connection point on the top that leads back to the central node, and no connection point on the bottom. But the nodes on the in-flow side have a connection point on the top that is unused. This seems to imply a possibility of showing multi-hop flows, but that doesn't seem to be possible with this widget. Until such capability is added, the connection points on top of the in-flows should be removed.

Acceptance criteria

• [ ] Satisfies entire acceptance criteria
• [ ] Analytics capturing is added (Optional)
• [ ] Consider demo & communication (Optional)
• [ ] Follow-up ideas & considerations get noted (Optional)
• [ ] Stakeholders approve (Optional)
• [ ] Code review is approved by at least 2 reviewers
• [ ] Tested by Elvijs/QA & discovered bugs resolved
• [ ] Documentation updated
• [ ] Assignee/opened by merges PR
• [ ] Automated E2E tests for happy path
• [ ] Code is merged
• [ ] Observability of critical user path
• [ ] Checked with target user persona

Links/Resources

• https://console.superfluid.finance/arbitrum-one/accounts/0xf45349435c4A7cbb519987bd4d7460479568fD63?tab=map

Readiness criteria

• [X] Descriptive title
• [X] Written as a user story: “As a [persona] who [context], I want to [do X] because [reason] , so that [outcome].”
• [ ] Acceptance criteria complying with Definition of Done
• [ ] User Persona/Target Audience: If User Persona is known otherwise assume Target audience
• [ ] Estimate/Story points
• [ ] Deadline: If not a part of an epic
• [ ] Priority: Reflected as order on the board, walking the board from the top and right
• [ ] Assignee
• [ ] Labels
• [ ] Link to epic: If belonging to an epic
• [ ] UI/UX Design (optional)
• [ ] Blockers/Prerequisites (optional): Use Zenhub blocked by/blocking feature
• [ ] Mood (optional): What mood is the user in when interfacing with this? Exploring? Stressed? Playful?