ArduPilot / ArduPilot/UAVLogViewer
Rework Plotly-Cesium interactions
Open
- Dominant language
- JavaScript
- Stars
- 258
- Forks
- 296
- PR merge metrics
- No merged PRs in 30d
Description
Currently there are events flowing in both directions, it should be possible to clean this up.
(maybe track the current state of the aircraft globally?)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or entry points. Start by tracing the events flowing between Plotly and Cesium and documenting where aircraft state is currently held; define the desired state ownership and verify that interactions work without redundant two-way event flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100