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

Option to avoid history tracking in wnfs #426

Open
Tracked by #501
gotjoshua opened this issue Oct 30, 2022 · 1 comment
Open
Tracked by #501

Option to avoid history tracking in wnfs #426

gotjoshua opened this issue Oct 30, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@gotjoshua
Copy link

Summary

When writing many small files to a folder in wnfs, each new file creates a new nested history entry in the previous folder. This is not needed in my use case (as the files are actually history tracking CRDT records in and of them selves).

Problem

This creates an unnecessarily deep and complex nested DAG situation.
It even rendered my gotjoshua account completely useless.

Impact

I must say I find these template headers annoyingly overlapping and I do not enjoy attempting to comply.

Solution

my ideas:

  1. inhibit history via a config option passed to wnfs add and/or publish
await fs.[add | publish](
  wn.path.file("public", "path", "to", "a", "file"),
  content,
  { history: false }
)
  1. add a .historyignore file to any folder to permanently avoid history tracking for that specific folder
    • needs consideration about recursion

Describe alternatives you've considered
I tried deleting stuff, but of course its still in the history (and i guess the delete action also deepens the DAG)

@icidasset
Copy link
Contributor

Will be implemented when Webnative ships with rs-wnfs as the primary file system implementation. There's already a hint of this in the codebase, see "history stepping": https://github.com/fission-codes/webnative/blob/e323e8ea5ffa7861f546773db15c6ea29e305395/src/fs/filesystem.ts#L541

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants