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

Better craftsmanship for Debugging Tools #4744

Closed
SamBroner opened this issue Jan 6, 2021 · 0 comments
Closed

Better craftsmanship for Debugging Tools #4744

SamBroner opened this issue Jan 6, 2021 · 0 comments
Assignees
Labels
area: dev experience Improving the experience of devs building on top of fluid area: tools

Comments

@SamBroner
Copy link
Contributor

SamBroner commented Jan 6, 2021

We have a group of valuable test/debugging libraries. We should make them more accessible, better documented and out word facing.

  1. Replay Tool
    Takes in a doc and creates a snapshot at a sequence #. Very useful for learning and visualization. Assumes we only use a specific set of DDSs
  2. Fluid Debugger
    Adapter on the storage interface that is enabled through the browser. Let's you choose to load from a specific snapshot and run op by op through the doc. Can load files from disk using the Replay tool
  3. Fetch Tool
    Download all ops and snapshots from storage. Relies on service drivers. Fetch tool feeds into the Replay tool
  4. Anonymizer
    Remove user data from snapshots. Only useable on test documents?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: dev experience Improving the experience of devs building on top of fluid area: tools
Projects
None yet
Development

No branches or pull requests

3 participants