Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

graph-saving: Make a graph's screenshot the saved graph

Aperta
  • Qualcosa non va?
#862 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@sanjeetyellu ci sta già lavorando.

Dal 16/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

by: ai-assisted frontend spike
Exploring

Saving a graph produces an image of it that also carries the graph's data inside the image file. It previews anywhere an image does (Slack, design reviews, docs), and dropping or pasting it into Argos turns it back into a zoomable graph. Nothing is stored in a database.

Hypothesis

The data inside the image survives the places engineers actually share images (Slack uploads, Drive, email attachments), and a pasted or dropped image re-renders in Argos the same as the original graph.

Context transfer
SUMMARY
#842: save, reopen, and zoom graphs inside Argos. Saved graphs must survive a local data upload and database wipe, and work for any static graph in Argos.

CONTEXT
- runId is SERIAL (scylla-server/migrations/2024-11-10-031516_create_all). After a wipe numbering restarts, so a stored runId can point at a different Run.
- Every chart in angular-client is ApexCharts (ng-apexcharts): components/graph, components/double-line-graph, components/pie-chart, pages/graph-page/graph.
- The graph page's historical range is capped at 7 days because high-rate telemetry means tens of millions of rows (MAX_RANGE_MINUTES).
- Later goal (not a storage requirement): a reopened saved graph keeps plotting while live telemetry streams onto the same chart. Today the graph page is either live or historical, never both at once.
- Chart: ApexCharts (ng-apexcharts); its toolbar is not disabled, so its built-in image download is likely already available.
- Some services recompress uploaded images, which can drop extra data in the file; which ones do is unknown.
Lingua principale
TypeScript
Stelle
5
Fork
1
Merge medio
2g 20h
PR unite (30g)
48

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Northeastern-Electric-Racing/Argos

Tutte le issue di Northeastern-Electric-Racing/Argos

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.