Vector35 / Vector35/binaryninja-api

Show a log of changes for each snapshot

Aperta
#6,346 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Component: UI Effort: Medium Impact: High
Lingua principale
C++
Stelle
1.3k
Fork
298
Merge medio
5g 5h
PR unite (30g)
19

Descrizione

What is the feature you'd like to have?
Enterprise users have wanted a way to view what has changed within a given snapshot since we've released the product. As a stop-gap, we've introduced a "commit message" where users can describe changes, and a "File Changelog..." dialog where users can view them. But, users (even non-Enterprise ones) have requested this.

Conceptually, I think this should be 'simple', since we should already have the metadata required to implement this. In reality, I think this will be difficult as we'll need to be able to show this to users in a way that makes sense to them and avoids performance issues.

Is your feature request related to a problem?
Users would like to know what has changed within a given snapshot. This is mostly relevant to Enterprise users where you are pulling in changes from other users and you want to know what changed. But, it's also relevant to non-Enterprise users that are receiving databases from others. And, as we continue to add ways for users to interact with their database, perform additional analysis with plugins, and so on, it would be great to have this functionality in the core product rather than just Ultimate/Enterprise.

Additional Information:
Issue migrated here from the internal Enterprise issue tracker.

We should also try and consider a future where we might want to let users remove a particular change from a snapshot (e.g. rewrite it without a given thing) when we implement this, at least from a UI/UX perspective. This is also desired, but is a considerable leap in difficulty-to-implement and not planned in any current roadmap.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

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.

Direzione di ricerca

Start by examining the existing "commit message" metadata and the "File Changelog..." dialog, then map how snapshot changes are represented and presented. Done means users can understand what changed in a snapshot without unacceptable performance, while leaving removal or rewriting of individual changes out of scope.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
cpp
Ambito
reverse-engineering
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.