Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-frame tracing user interaction #71

Open
laike9m opened this issue Nov 8, 2020 · 1 comment
Open

Multi-frame tracing user interaction #71

laike9m opened this issue Nov 8, 2020 · 1 comment

Comments

@laike9m
Copy link
Owner

laike9m commented Nov 8, 2020

On the backend, frames are stored in a tree

UI interaction:

Picking frames

  1. User clicks on a location in VSC
  2. Extension sends a location to backend
  3. Backend returns the first 5 frames that contain the specified code location, with
    the callsite location.
    (In the future we can extend the max number of candidates.)
  4. User picks a frame
  5. The identity of the picked frame is sent to backend
  6. Backend sends back tracing results for the picked frame

Steps 2 ~ 5 won't happen if there's only one frame.

If there's no frame that matches the current location, nothing will happen.

Map tracing result to code
TBD. But for now, we should prevent frame selection process from happening (again) if
tracing is present and code location didn't go out of the frame's scope.

By default, we should show previous frame + current frame + 1-level frames derived
from the current frame. We will let users configure this on extension UI.

@laike9m laike9m created this issue from a note in Cyberbrain's Kanban (To do) Nov 8, 2020
@laike9m laike9m added the vision label Nov 8, 2020
@laike9m laike9m moved this from To do to Vision in Cyberbrain's Kanban Nov 14, 2020
@laike9m
Copy link
Owner Author

laike9m commented Nov 14, 2020

Related #73

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant