John Vilk
John Vilk
Note that this bug causes a memory leak, as the `eldata` variable grows without bound as new data is added without being removed.
@davidjmcclelland I have a fix open in a PR here: https://github.com/DmitryBaranovskiy/raphael/pull/1077 It's a one line fix that's easy to apply.
@davidjmcclelland is this code open source, by any chance? (I'm not promising anything, but I've been on a bit of a JS memory leak bent.) And is this browser specific?...
The project looks unfortunately dead, so I doubt it'll ever get merged in. :frowning:
@pyramation I don't believe any backend currently supports symlinks. The basic abstraction is there should someone want to implement a backend that supports them, but I never got around to...
The contents of a symlink is the path to the file you're symlinking. So a symlink to `../foo` will contain `../foo`. It's symbolic, so if you delete `../foo` and bring...
This could be added to all backends via [`BaseFileSystem`](https://github.com/jvilk/BrowserFS/blob/master/src/core/file_system.ts#L385) and [`SynchronousFileSystem`](https://github.com/jvilk/BrowserFS/blob/master/src/core/file_system.ts#L798). I'd like to wait until it's stable in Node, though.
Thanks for the note!
Good find. There's likely a bug in https://github.com/jvilk/bfs-path
I'd accept PRs for this. If you only care about _local_ modifications to the filesystem (meaning: you don't care about watching Dropbox files for changes, or another browser tab interfacing...